Problem Note 69123: Running PROC CONTENTS on an Oracle or Sybase PROC ACCESS view descriptor might result in an error
 |  |  |  |  |
Running the CONTENTS procedure against an Oracle or SAP ASE view descriptor might result in a Segmentation Violation or Read Access Violation when the following is true:
- You run on a Microsoft Windows or UNIX operating system.
- The view descriptor was created using PROC ACCESS.
- You run SAS® 9.4M6 (TS1M6) and use the Oracle view descriptor.
- You run SAS® 9.4M7 (TS1M7) and use either the Oracle or SAP ASE view descriptor.
On a Windows system, the error might look similar to the following with Oracle:
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
Please contact technical support and provide them with the following traceback information:
The SAS task name is [CONTENTS]
ERROR: Read Access Violation CONTENTS
Exception occurred at (0B3643C1)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
000000000B3643C1 0000000036B12AF0 sasioora:\oryhem.c\yoeinfs 718
000000000ECFA6A2 0000000036B12AF8 sasyoio:tkvercn1+0x29662
000000000EB2C254 0000000036B12B48 sasqutil:tkvercn1+0x5B214
000000000EAFD6FF 0000000036B1BBB0 sasqutil:tkvercn1+0x2C6BF
000000000EAE0EB9 0000000036B1F5F0 sasqutil:tkvercn1+0xFE79
000000000EAF088A 0000000036B1F900 sasqutil:tkvercn1+0x1F84A
00000000059F00EF 0000000036B1F908 sasxshel:tkvercn1+0x4F0AF
000000000EB2EE93 0000000036B1FA20 sasqutil:tkvercn1+0x5DE53
000000000EAD14C9 0000000036B1FB20 sasqutil:tkvercn1+0x489
00000000035BA366 0000000036B1FB28 sashost:\vvtentr.c\vvtentr 311
00000000035C0574 0000000036B1FF20 sashost:\WX6htthread.c\htthread 126 +(0x9)
00007FF9C8C17034 0000000036B1FF28 KERNEL32:BaseThreadInitThunk+0x14
00007FF9CA242651 0000000036B1FF58 ntdll:RtlUserThreadStart+0x21
ERROR: Read Access Violation CONTENTS
Exception occurred at (0B3643C1)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
000000000B3643C1 0000000036B12AF0 sasioora:\oryhem.c\yoeinfs 718
000000000ECFA6A2 0000000036B12AF8 sasyoio:tkvercn1+0x29662
000000000EB2C254 0000000036B12B48 sasqutil:tkvercn1+0x5B214
000000000EAFD6FF 0000000036B1BBB0 sasqutil:tkvercn1+0x2C6BF
000000000EAE0EB9 0000000036B1F5F0 sasqutil:tkvercn1+0xFE79
000000000EAF088A 0000000036B1F900 sasqutil:tkvercn1+0x1F84A
00000000059F00EF 0000000036B1F908 sasxshel:tkvercn1+0x4F0AF
000000000EB2EE93 0000000036B1FA20 sasqutil:tkvercn1+0x5DE53
000000000EAD14C9 0000000036B1FB20 sasqutil:tkvercn1+0x489
00000000035BA366 0000000036B1FB28 sashost:\vvtentr.c\vvtentr 311
00000000035C0574 0000000036B1FF20 sashost:\WX6htthread.c\htthread 126 +(0x9)
00007FF9C8C17034 0000000036B1FF28 KERNEL32:BaseThreadInitThunk+0x14
00007FF9CA242651 0000000036B1FF58 ntdll:RtlUserThreadStart+0x21
On a Windows system, the error might look similar to the following with SAP ASE:
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
Please contact technical support and provide them with the following traceback information:
The SAS task name is [CONTENTS]
ERROR: Read Access Violation CONTENTS
Exception occurred at (3754D4EB)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
00007FF93754D4EB 00000020EADEA3F0 sasiosyb:tkvercn1+0x2C49B
00007FF93760BFDB 00000020EADEA3F8 sasyoio:tkvercn1+0x4AF8B
00007FF93748982B 00000020EADEA4B8 sasqutil:tkvercn1+0x987DB
00007FF937444FB8 00000020EADF7240 sasqutil:tkvercn1+0x53F68
00007FF93740F602 00000020EADFECE0 sasqutil:tkvercn1+0x1E5B2
00007FF9373F398B 00000020EADFF130 sasqutil:tkvercn1+0x293B
00007FF9373F2E10 00000020EADFF1B0 sasqutil:tkvercn1+0x1DC0
00007FF93A9979C8 00000020EADFF1B8 sasxshel:tkvercn1+0x76978
00007FF93749C22F 00000020EADFF450 sasqutil:tkvercn1+0xAB1DF
00007FF9373F1CD9 00000020EADFF740 sasqutil:tkvercn1+0xC89
00007FF9373F121C 00000020EADFF7C0 sasqutil:tkvercn1+0x1CC
00007FF93B143B28 00000020EADFF7C8 sashost:Main+0x24F01
00007FF93B14D9FA 00000020EADFFBD0 sashost:Main+0x2EDD3
00007FF9C8C17034 00000020EADFFBD8 KERNEL32:BaseThreadInitThunk+0x14
00007FF9CA242651 00000020EADFFC08 ntdll:RtlUserThreadStart+0x21
ERROR: Read Access Violation CONTENTS
Exception occurred at (3754D4EB)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
00007FF93754D4EB 00000020EADEA3F0 sasiosyb:tkvercn1+0x2C49B
00007FF93760BFDB 00000020EADEA3F8 sasyoio:tkvercn1+0x4AF8B
00007FF93748982B 00000020EADEA4B8 sasqutil:tkvercn1+0x987DB
00007FF937444FB8 00000020EADF7240 sasqutil:tkvercn1+0x53F68
00007FF93740F602 00000020EADFECE0 sasqutil:tkvercn1+0x1E5B2
00007FF9373F398B 00000020EADFF130 sasqutil:tkvercn1+0x293B
00007FF9373F2E10 00000020EADFF1B0 sasqutil:tkvercn1+0x1DC0
00007FF93A9979C8 00000020EADFF1B8 sasxshel:tkvercn1+0x76978
00007FF93749C22F 00000020EADFF450 sasqutil:tkvercn1+0xAB1DF
00007FF9373F1CD9 00000020EADFF740 sasqutil:tkvercn1+0xC89
00007FF9373F121C 00000020EADFF7C0 sasqutil:tkvercn1+0x1CC
00007FF93B143B28 00000020EADFF7C8 sashost:Main+0x24F01
00007FF93B14D9FA 00000020EADFFBD0 sashost:Main+0x2EDD3
00007FF9C8C17034 00000020EADFFBD8 KERNEL32:BaseThreadInitThunk+0x14
00007FF9CA242651 00000020EADFFC08 ntdll:RtlUserThreadStart+0x21
On a UNIX platform, the error might look similar to the following for Oracle:
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
Please contact technical support and provide them with the following traceback information:
The SAS task name is [CONTENTS]
Segmentation Violation
Traceback of the Exception:
/ada/opt/sas940/SASFoundation/9.4/sasexe/sas(+0x17d5fe) [0x55a4b90fd5fe]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sas(+0x503fe) [0x55a4b8fd03fe]
/ada/opt/sas940/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x14b) [0x7f0a185342db]
/lib64/libpthread.so.0(+0xf630) [0x7f0a19f0d630]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasioora(yoeinfs+0x135) [0x7f09ee9dd135]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasyoio(yoinfsy+0xba) [0x7f09eec8963a]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasqutil(zutinfd+0x23) [0x7f09ec46bf63]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasqutil(utconts+0xa439) [0x7f09ec447179]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasqutil(+0x1288a) [0x7f09ec42988a]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasqutil(utrstmt+0x799) [0x7f09ec43c549]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasxshel(yspproc+0x51e) [0x7f09fe228dae]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasqutil(sasqutil+0x3e9) [0x7f09ec41e3b9]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sas(vvtentr+0x17f) [0x55a4b8fcffbf]
/lib64/libpthread.so.0(+0x7ea5) [0x7f0a19f05ea5]
/lib64/libc.so.6(clone+0x6d) [0x7f0a194f1b0d]
Segmentation Violation
Traceback of the Exception:
/ada/opt/sas940/SASFoundation/9.4/sasexe/sas(+0x17d5fe) [0x55a4b90fd5fe]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sas(+0x503fe) [0x55a4b8fd03fe]
/ada/opt/sas940/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x14b) [0x7f0a185342db]
/lib64/libpthread.so.0(+0xf630) [0x7f0a19f0d630]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasioora(yoeinfs+0x135) [0x7f09ee9dd135]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasyoio(yoinfsy+0xba) [0x7f09eec8963a]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasqutil(zutinfd+0x23) [0x7f09ec46bf63]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasqutil(utconts+0xa439) [0x7f09ec447179]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasqutil(+0x1288a) [0x7f09ec42988a]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasqutil(utrstmt+0x799) [0x7f09ec43c549]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasxshel(yspproc+0x51e) [0x7f09fe228dae]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sasqutil(sasqutil+0x3e9) [0x7f09ec41e3b9]
/ada/opt/sas940/SASFoundation/9.4/sasexe/sas(vvtentr+0x17f) [0x55a4b8fcffbf]
/lib64/libpthread.so.0(+0x7ea5) [0x7f0a19f05ea5]
/lib64/libc.so.6(clone+0x6d) [0x7f0a194f1b0d]
On a UNIX platform, the error might look similar to the following for SAP ASE:
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
Please contact technical support and provide them with the following traceback information:
The SAS task name is [CONTENTS]
Segmentation Violation
Traceback of the Exception:
/sasgen/dev/mva-v940m7/SAS/laxnd/sas(+0x3502cd) [0x7f00e64f22cd]
/sasgen/dev/mva-v940m7/SAS/laxnd/sas(+0x35022f) [0x7f00e64f222f]
/sasgen/dev/mva-v940m7/SAS/laxnd/sas(+0xb18a7) [0x7f00e62538a7]
/sasgen/dev/mva-v940m7/SAS/laxnd/sas(+0xb11ca) [0x7f00e62531ca]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/tkmk.so(bkt_signal_handler+0x410) [0x7f00e41e716a]
/lib64/libpthread.so.0(+0x30aa00f7e0) [0x7f00e5b537e0]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasiosyb(yoeinfs+0x135) [0x7f00b7aa0b4d]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasyoio(yoinfsy+0x26b) [0x7f00b7d6bc2f]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(zutinfd+0x66) [0x7f00ac4c44f4]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(utconts+0x192fc) [0x7f00ac47e090]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(+0x2b357) [0x7f00ac447357]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(+0xe83e) [0x7f00ac42a83e]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(utrstmt+0x12f) [0x7f00ac429b1c]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasxshel(yspproc+0xfc7) [0x7f00c94364a0]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(xsparse+0x1b1) [0x7f00ac4ccd99]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(+0xc89d) [0x7f00ac42889d]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(sasqutil+0x1cf) [0x7f00ac427d43]
/sasgen/dev/mva-v940m7/SAS/laxnd/sas(vvtentr+0x31c) [0x7f00e6252fcc]
/lib64/libpthread.so.0(+0x30aa007aa1) [0x7f00e5b4baa1]
/lib64/libc.so.6(clone+0x6d) [0x7f00e51d9c4d]
Segmentation Violation
Traceback of the Exception:
/sasgen/dev/mva-v940m7/SAS/laxnd/sas(+0x3502cd) [0x7f00e64f22cd]
/sasgen/dev/mva-v940m7/SAS/laxnd/sas(+0x35022f) [0x7f00e64f222f]
/sasgen/dev/mva-v940m7/SAS/laxnd/sas(+0xb18a7) [0x7f00e62538a7]
/sasgen/dev/mva-v940m7/SAS/laxnd/sas(+0xb11ca) [0x7f00e62531ca]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/tkmk.so(bkt_signal_handler+0x410) [0x7f00e41e716a]
/lib64/libpthread.so.0(+0x30aa00f7e0) [0x7f00e5b537e0]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasiosyb(yoeinfs+0x135) [0x7f00b7aa0b4d]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasyoio(yoinfsy+0x26b) [0x7f00b7d6bc2f]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(zutinfd+0x66) [0x7f00ac4c44f4]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(utconts+0x192fc) [0x7f00ac47e090]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(+0x2b357) [0x7f00ac447357]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(+0xe83e) [0x7f00ac42a83e]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(utrstmt+0x12f) [0x7f00ac429b1c]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasxshel(yspproc+0xfc7) [0x7f00c94364a0]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(xsparse+0x1b1) [0x7f00ac4ccd99]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(+0xc89d) [0x7f00ac42889d]
/sasgen/dev/mva-v940m7/sasdvd/com/laxnd/sasqutil(sasqutil+0x1cf) [0x7f00ac427d43]
/sasgen/dev/mva-v940m7/SAS/laxnd/sas(vvtentr+0x31c) [0x7f00e6252fcc]
/lib64/libpthread.so.0(+0x30aa007aa1) [0x7f00e5b4baa1]
/lib64/libc.so.6(clone+0x6d) [0x7f00e51d9c4d]
There is no workaround for using the view descriptor. However, you can do the following:
- Create an explicit pass-through query that replicates the results of what the access view descriptor would have generated.
- Create an SQL view using the pass-through query that you created in step 1.
- Use the SQL view that you created instead of the view descriptor.
PROC CV2VIEW is not an option to convert the access view to an SQL view.
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 | SAS Release | |
| Reported | Fixed* | |||
| SAS System | Base SAS | Microsoft® Windows® for x64 | 9.4 TS1M6 | |
| Microsoft Windows 8 Enterprise 32-bit | 9.4 TS1M6 | |||
| Microsoft Windows 8 Enterprise x64 | 9.4 TS1M6 | |||
| Microsoft Windows 8 Pro 32-bit | 9.4 TS1M6 | |||
| Microsoft Windows 8 Pro x64 | 9.4 TS1M6 | |||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4 TS1M6 | |||
| Microsoft Windows 8.1 Enterprise x64 | 9.4 TS1M6 | |||
| Microsoft Windows 8.1 Pro 32-bit | 9.4 TS1M6 | |||
| Microsoft Windows 8.1 Pro x64 | 9.4 TS1M6 | |||
| Microsoft Windows 10 | 9.4 TS1M6 | |||
| Microsoft Windows Server 2008 | 9.4 TS1M6 | |||
| Microsoft Windows Server 2008 R2 | 9.4 TS1M6 | |||
| Microsoft Windows Server 2008 for x64 | 9.4 TS1M6 | |||
| Microsoft Windows Server 2012 Datacenter | 9.4 TS1M6 | |||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4 TS1M6 | |||
| Microsoft Windows Server 2012 R2 Std | 9.4 TS1M6 | |||
| Microsoft Windows Server 2012 Std | 9.4 TS1M6 | |||
| Microsoft Windows Server 2016 | 9.4 TS1M6 | |||
| Microsoft Windows Server 2019 | 9.4 TS1M6 | |||
| Windows 7 Enterprise 32 bit | 9.4 TS1M6 | |||
| Windows 7 Enterprise x64 | 9.4 TS1M6 | |||
| Windows 7 Home Premium 32 bit | 9.4 TS1M6 | |||
| Windows 7 Home Premium x64 | 9.4 TS1M6 | |||
| Windows 7 Professional 32 bit | 9.4 TS1M6 | |||
| Windows 7 Professional x64 | 9.4 TS1M6 | |||
| Windows 7 Ultimate 32 bit | 9.4 TS1M6 | |||
| Windows 7 Ultimate x64 | 9.4 TS1M6 | |||
| 64-bit Enabled AIX | 9.4 TS1M6 | |||
| 64-bit Enabled Solaris | 9.4 TS1M6 | |||
| HP-UX IPF | 9.4 TS1M6 | |||
| Linux for x64 | 9.4 TS1M6 | |||
| Solaris for x64 | 9.4 TS1M6 | |||
A fix for this issue for SAS/ACCESS Interface to Oracle 9.44 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/J8P.html#69123A fix for this issue for SAS/ACCESS Interface to SAP ASE 9.4_M6 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/L6U.html#69123| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2022-06-20 15:58:45 |
| Date Created: | 2022-04-24 13:26:50 |