SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 44257: A segmentation violation might occur and your server might not function when you run a SAS® Stored Process that accesses a database

DetailsHotfixAboutRate It

When you run code on the SAS® Stored Process Server or on the SAS/IntrNet® application server, a segmentation violation (or access violation) might occur. The problem happens when the code accesses a database and tracing is turned on (via the SASTRACE= option).

In particular, the problem happens when a SAS Stored Process uses SQL procedure code to access an Oracle, Netezza, DB2, Microsoft SQL Server, or Teradata database. (It is possible, too, that other databases might experience this problem.)

In some cases, the server also might stop functioning after the problem occurs. When the server stops, the SAS Stored Process log file might contain a message similar to the following before the segmentation violation occurs:

ORACLE_25: Prepared: on connection 0
SELECT * FROM SOMELIB.SOME_TABLE_HERE

You can either work around this problem or you can download a hot fix.

Click the Hot Fix tab in this note to access the hot fix for this issue.

If you prefer to use the workaround, you need to locate and remove the following OPTIONS statement from your code:

options sastrace=",,,d" sastraceloc=saslog no$stsuffix;

Note: If you are not sure whether tracing is turned on (because, for example, you either do not have access to the code or you have a very large amount of code to search), the following technique can be helpful. Add the following statements to the code that is experiencing the segmentation violation:

%let traceopt = %sysfunc(getoption(sastrace)); %put *SASTRACE option setting is: &traceopt*;

These statements generate output that indicates whether tracing is on. When tracing is on, the SASTRACE= option appears in the output with a non-blank character value (for example, ",,,d"). In that case, you (or whoever maintains the affected code) should locate and remove the appropriate OPTIONS statement.

If you experience the problem described in this note but the workaround shows that tracing is not turned on, contact SAS Technical Support for further help.



Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemSAS Integration Technologiesz/OS9.2 TS2M09.3 TS1M2
Microsoft® Windows® for 64-Bit Itanium-based Systems9.2 TS2M09.3 TS1M2
Microsoft Windows Server 2003 Datacenter 64-bit Edition9.2 TS2M09.3 TS1M2
Microsoft Windows Server 2003 Enterprise 64-bit Edition9.2 TS2M09.3 TS1M2
Microsoft Windows XP 64-bit Edition9.2 TS2M09.3 TS1M2
Microsoft® Windows® for x649.2 TS2M09.3 TS1M2
Microsoft Windows Server 2003 Datacenter Edition9.2 TS2M09.3 TS1M2
Microsoft Windows Server 2003 Enterprise Edition9.2 TS2M09.3 TS1M2
Microsoft Windows Server 2003 Standard Edition9.2 TS2M09.3 TS1M2
Microsoft Windows Server 2003 for x649.2 TS2M09.3 TS1M2
Microsoft Windows Server 2008 for x649.2 TS2M09.3 TS1M2
Microsoft Windows XP Professional9.2 TS2M09.3 TS1M2
Windows Vista9.2 TS2M09.3 TS1M2
Windows Vista for x649.2 TS2M09.3 TS1M2
64-bit Enabled AIX9.2 TS2M09.3 TS1M2
64-bit Enabled HP-UX9.2 TS2M09.3 TS1M2
64-bit Enabled Solaris9.2 TS2M09.3 TS1M2
HP-UX IPF9.2 TS2M09.3 TS1M2
Linux9.2 TS2M09.3 TS1M2
Linux for x649.2 TS2M09.3 TS1M2
OpenVMS on HP Integrity9.2 TS2M09.3 TS1M2
Solaris for x649.2 TS2M09.3 TS1M2
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.