Problem Note 57014: Using a PUT function with SAS/ACCESS® Interface to ODBC might cause a segmentation violation in Base SAS®
 |  |  |  |  |
Under some circumstances, the use of a SAS PUT function might cause Base SAS to return a segmentation violation. And as a result, you have to restart Base SAS and any BI Clients that use Base SAS. For example, a PUT function causes this issue when the function is used with the SAS/ACCESS Interface to ODBC product.
Example
libname myconn odbc dsn=data-source user=user-id pwd=password schema=schema-name; proc sql; select distinct mycol1 , put(mycol1,$fmtprovider.) from myconn.mytable; quit; ERROR: An exception has been encountered. Please contact technical support and provide them with the following traceback information: The SAS task name is [SQL (2) ] Segmentation Violation Traceback of the Exception: /SAS_9.3/SASFoundation/9.3/sasexe/sas() [0x5165ad] /SAS_9.3/SASFoundation/9.3/sasexe/sas() [0x41e9f8] /SAS_9.3/SASFoundation/9.3/sasexe/sas() [0x41e6cf] /SAS_9.3/SASFoundation/9.3/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f45d34b26e4] /lib64/libpthread.so.0() [0x34d3c0f500] /SAS_9.3/SASFoundation/9.3/sasexe/tkeodbc.so(odbcEnvFreeHandle+0x28) [0x7f45840e4a88] /SAS_9.3/SASFoundation/9.3/sasexe/tkedcm.so(dcmEnvFreeHandle+0x6a) [0x7f458499966a] /SAS_9.3/SASFoundation/9.3/sasexe/tkepre.so(preEnvFreeHandle+0x347) [0x7f4584490567] /SAS_9.3/SASFoundation/9.3/sasexe/tkiog.so(TKIOGConDestroy+0x148) [0x7f4584acde18] /SAS_9.3/SASFoundation/9.3/sasexe/tkiog.so(TKIOGAllocConnectionWithString+0x1e4) [0x7f4584acd494] /SAS_9.3/SASFoundation/9.3/sasexe/sasxog(yogConLib+0x59b) [0x7f4584c2045b] /SAS_9.3/SASFoundation/9.3/sasexe/sasxog(yogConFid+0x39) [0x7f4584c1feb9] /SAS_9.3/SASFoundation/9.3/sasexe/sasxog(yogAllocConnectionWithFid+0x48) [0x7f4584c1e808] /SAS_9.3/SASFoundation/9.3/sasexe/sassqlu(+0x33bc9) [0x7f4584d80bc9] /SAS_9.3/SASFoundation/9.3/sasexe/sassqlu(+0x3006b) [0x7f4584d7d06b] /SAS_9.3/SASFoundation/9.3/sasexe/sassqlu(+0x2bfed) [0x7f4584d78fed] /SAS_9.3/SASFoundation/9.3/sasexe/sassqlu(+0x2a486) [0x7f4584d77486] /SAS_9.3/SASFoundation/9.3/sasexe/sassqlu(+0x21aae) [0x7f4584d6eaae] /SAS_9.3/SASFoundation/9.3/sasexe/sassqlu(+0x2a27e) [0x7f4584d7727e] /SAS_9.3/SASFoundation/9.3/sasexe/sassqlu(+0x2eb9c) [0x7f4584d7bb9c] /SAS_9.3/SASFoundation/9.3/sasexe/sassqlu(+0x378e2) [0x7f4584d848e2] /SAS_9.3/SASFoundation/9.3/sasexe/sassqlu(+0x1df1f) [0x7f4584d6af1f] /SAS_9.3/SASFoundation/9.3/sasexe/sassqlu(+0x2608e) [0x7f4584d7308e] /SAS_9.3/SASFoundation/9.3/sasexe/sassqlu(+0x2a27e) [0x7f4584d7727e] /SAS_9.3/SASFoundation/9.3/sasexe/sassqlu(sqltxt2+0x3e6) [0x7f4584d61666] /SAS_9.3/SASFoundation/9.3/sasexe/sassqlp(+0x60183) [0x7f459d43d183]
With Base SAS 9.3 TS1M2, you must apply a hot fix AND use the following option to prevent the pushdown from happening:
options sqlmapputto=none;
The hot fix enables SAS 9.3 TS1M2 to honor the SQLMAPPUTTO system option.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | Base SAS | Microsoft® Windows® for x64 | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 |
| Microsoft Windows 8 Enterprise 32-bit | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Enterprise x64 | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Pro 32-bit | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8 Pro x64 | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Enterprise x64 | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Pro | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows 8.1 Pro 32-bit | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2008 | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2008 R2 | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2008 for x64 | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 Datacenter | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 R2 Datacenter | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 R2 Std | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Microsoft Windows Server 2012 Std | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Enterprise 32 bit | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Enterprise x64 | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Home Premium 32 bit | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Home Premium x64 | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Professional 32 bit | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Professional x64 | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Ultimate 32 bit | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Windows 7 Ultimate x64 | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| 64-bit Enabled AIX | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| 64-bit Enabled HP-UX | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| 64-bit Enabled Solaris | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| HP-UX IPF | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Linux | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Linux for x64 | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
| Solaris for x64 | 9.3_M2 | 9.4_M3 | 9.3 TS1M2 | 9.4 TS1M3 | ||
A fix for this issue for Base SAS 9.4_M3 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/V01.html#57014A fix for this issue for Base SAS 9.4_M2 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/R19.html#57014A fix for this issue for Base SAS 9.3_M2 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/I22.html#57014| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2015-12-15 12:35:00 |
| Date Created: | 2015-11-05 08:52:12 |