Problem Note 64700: SAS® Studio stops responding and the CAS log shows an access violation when you load an ORACLE table using PROC CASUTIL in SAS® Data Connector to ODBC
 |  |  |  |  |
When you use the CASUTIL procedure to load Oracle tables in SAS Data Connector to ODBC, SAS Studio stops responding and you see an access violation similar to the following in the CAS log:
/opt/sas/viya/home/SASFoundation/sasexe/tkcasdrv.so(tktracex+0x42)
[0x7f4bae37ec92]
/opt/sas/viya/home/SASFoundation/sasexe/tkcasdrv.so(exceptionHandler+0x1cd)
[0x7f4bae323d6d]
/opt/sas/viya/home/SASFoundation/sasexe/tkmk.so(bktExcept+0x5b) [0x7f4bb9a7349b]
/opt/sas/viya/home/SASFoundation/sasexe/tkmk.so(bkt_signal_handler+0x169)
[0x7f4bb9a73b89]
/lib64/libpthread.so.0(+0xf5d0) [0x7f4bbb1b95d0]
/opt/sas/viya/home/SASFoundation/sasexe/tkmk.so(skm_frontlink+0x89)
[0x7f4bb9a8d429]
/opt/sas/viya/home/SASFoundation/sasexe/tkmk.so(skmMemRelease+0x31f)
[0x7f4bb9a8975f]
/opt/sas/viya/home/SASFoundation/sasexe/tketsb.so(tketsbAixDestroy+0x60)
[0x7f4b89de9050]
/opt/sas/viya/home/SASFoundation/sasexe/tketsb.so(tketsbFreeStmt+0x56a)
[0x7f4b89de8dca]
/opt/sas/viya/home/SASFoundation/sasexe/tkeodbc.so(odbcFreeStmt+0xbb)
[0x7f4b8ac11b4b]
/opt/sas/viya/home/SASFoundation/sasexe/tketrc.so(trcFreeStmt+0xcc)
[0x7f4b8a4f12fc]
/opt/sas/viya/home/SASFoundation/sasexe/tkedcm.so(dcmFreeStmt+0x1b4)
[0x7f4b8bb19354]
/opt/sas/viya/home/SASFoundation/sasexe/tkedcm.so(dcmStmtFreeHandle+0x3e)
[0x7f4b8bb190ae]
/opt/sas/viya/home/SASFoundation/sasexe/tkepre.so(preStmtFreeHandle+0x35d)
[0x7f4b8b0f698d]
/opt/sas/viya/home/SASFoundation/sasexe/tkcastkts.so(+0x7b0d2) [0x7f4b908630d2]
/opt/sas/viya/home/SASFoundation/sasexe/tkcastkts.so(+0x6f8a4) [0x7f4b908578a4]
/opt/sas/viya/home/SASFoundation/sasexe/tkcasddsodbc.so(ddstktsLoadTable+0x2f8)
[0x7f4b90c33d68]
/opt/sas/viya/home/SASFoundation/sasexe/tkcastab.so(LoadTable+0x259a)
[0x7f4babc556ca]
/opt/sas/viya/home/SASFoundation/sasexe/tkcasa.so(casaInvoke+0x2022)
[0x7f4ba55f2ad2]
/opt/sas/viya/home/SASFoundation/sasexe/tkcasdrv.so(HandleActionControllerThread
+0xce2) [0x7f4bae32e622]
/opt/sas/viya/home/SASFoundation/sasexe/tkmk.so(sktMain+0xf7) [0x7f4bb9a71367]
/opt/sas/viya/home/SASFoundation/sasexe/tkmk.so(bktMain+0x78) [0x7f4bb9a732b8]
/lib64/libpthread.so.0(+0x7dd5) [0x7f4bbb1b1dd5]
/lib64/libc.so.6(clone+0x6d) [0x7f4bba79dead]
This problem occurs because the Oracle ODBC driver uses 64-bit values for row status array, which does not match the ODBC specifications. The SAS Data Connector to ODBC allocates 32-bit values in the row status array. Because the allocated size is too small, an error occurs.
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Data Connector to ODBC | Linux for x64 | V.03.04 | V.03.05 | Viya | Viya |
| Microsoft® Windows® for x64 | V.03.04 | V.03.05 | Viya | Viya | ||
An update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Linux Deployment Guide at
http://documentation.sas.com/?softwareId=administration&softwareVersion=3.4&softwareContextId=softwareUpdatesViya on Linux: An update for this issue is available for SAS Viya 3.4. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.4 for Linux Deployment Guide at
http://documentation.sas.com/?softwareId=administration&softwareVersion=3.4&softwareContextId=softwareUpdates| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2019-10-31 15:38:21 |
| Date Created: | 2019-08-28 09:13:07 |