Problem Note 69708: A segmentation violation occurs in SAS® Federation Server 4.4 when executing the SQLSTMT DS2 package against SQL Server or Oracle with long data types
You might encounter an issue on SAS Federation Server 4.4 under the following conditions:
- You run DS2 code with the SQLSTMT DS2 package.
- You run the code against long data types.
- You use a VARCHAR data type that exceeds 1,024 characters in Linux environments and 4,096 characters in Microsoft Windows environments.
Here is example code that triggers this issue:
dcl package sqlstmt query('select charge_group_code, data_dictionary_code, data_dictionary_name, data_dictionary_description from "test"."dbo"."charge_group_codes" where "data_dictionary_code"=?', [value]);
method run();
this.value = 29;
rc = query.execute();
if (rc = 0) then do;
rc = query.bindResults([charge_group_code, data_dictionary__code, data_dictionary_name, data_dictionary_description]);
rc = query.fetch();
put data_dictionary__code=;
put charge_group_code=;
put data_dictionary_name=;
end;
end;
When you run code similar to the example above, a segmentation violation similar to the following occurs in a stack backtrace:
2022-07-28T15:56:19,048 ERROR [00000158] App.Program 4:sasdemo - /opt/sas/sashome/SASFoundation/9.4/sasexe/tkepre.so(tktracex+0x2e) [0x7fd501d3270e]
/opt/sas/sashome/SASFoundation/9.4/sasexe/tkepre.so(preExceptionHandler+0x88) [0x7fd501d009b8]
/opt/sas/sashome/SASFoundation/9.4/sasexe/tkmk.so(bktExcept+0x51) [0x7fd50f371ce1]
/opt/sas/sashome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x14b) [0x7fd50f3722db]
/usr/lib64/libpthread.so.0(+0xf630) [0x7fd510b35630]
/opt/sas/sashome/AccessClients/9.4/FederationServer/lib/S0sqls28.so(+0x282ca3) [0x7fd4bc832ca3]
/opt/sas/sashome/AccessClients/9.4/FederationServer/lib/S0sqls28.so(SQLColAttributeW+0x4f) [0x7fd4bc70dd51]
/opt/sas/sashome/AccessClients/9.4/FederationServer/lib/libodbc.so(+0xc9bf4) [0x7fd4be6e2bf4]
/opt/sas/sashome/AccessClients/9.4/FederationServer/lib/libodbc.so(+0xc90d5) [0x7fd4be6e20d5]
/opt/sas/sashome/AccessClients/9.4/FederationServer/lib/libodbc.so(SQLColAttributeW+0x13a) [0x7fd4be6c9414]
/opt/sas/sashome/SASFoundation/9.4/sasexe/tkeodbc.so(odbcColAttrArray+0x522) [0x7fd4be97ce92]
The same issue occurs when you use a CLOB data type in Oracle.
The only workaround is to use a VARCHAR data type with a fixed length within the queried database table.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Federation Server | Microsoft® Windows® for x64 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows 8 Enterprise 32-bit | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows 8 Enterprise x64 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows 8 Pro 32-bit | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows 8 Pro x64 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows 8.1 Enterprise 32-bit | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows 8.1 Enterprise x64 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows 8.1 Pro 32-bit | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows 8.1 Pro x64 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows 10 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows 11 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows Server 2008 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows Server 2008 R2 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows Server 2008 for x64 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows Server 2012 Datacenter | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows Server 2012 R2 Datacenter | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows Server 2012 R2 Std | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows Server 2012 Std | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows Server 2016 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows Server 2019 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Microsoft Windows Server 2022 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Windows 7 Enterprise 32 bit | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Windows 7 Enterprise x64 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Windows 7 Home Premium 32 bit | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Windows 7 Home Premium x64 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Windows 7 Professional 32 bit | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Windows 7 Professional x64 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Windows 7 Ultimate 32 bit | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Windows 7 Ultimate x64 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
64-bit Enabled AIX | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
64-bit Enabled Solaris | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
HP-UX IPF | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Linux for x64 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
Solaris for x64 | 4.4 | 4.5 | 9.4 TS1M7 | 9.4 TS1M8 |
*
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.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2023-01-11 09:21:55 |
Date Created: | 2022-11-18 10:01:33 |