Problem Note 70582: A Read access violation or segmentation violation occurs when registering DB2 Tables with foreign keys in the SAS® metadata
 |  |  |  |  |
When attempting to register a new DB2 table or update an existing DB2 table in SAS Metadata, a segmentation violation or Read access violation similar to the following might occur in the SAS log:
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [METALIB ]
Segmentation Violation
Traceback of the Exception:
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sas(+0x185ed2) [0x56365a16eed2]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sas(+0x4c60c) [0x56365a03560c]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x14b) [0x7f054eb6e70b]
/lib64/libpthread.so.0(+0x12cf0) [0x7f055042acf0]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sasmetas(addForKeys+0x1f0) [0x7f0506769af0]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sasmetas(addmeta+0x329) [0x7f0506743559]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sasmetas(refmeta+0x1246) [0x7f050673eb36]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sasmetas(sasmetas+0x2d10) [0x7f05067321c0]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sas(+0x4c1eb) [0x56365a0351eb]
/lib64/libpthread.so.0(+0x81ca) [0x7f05504201ca]
/lib64/libc.so.6(clone+0x43) [0x7f054f8dce73]
Please contact technical support and provide them with the following traceback information:
The SAS task name is [METALIB ]
Segmentation Violation
Traceback of the Exception:
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sas(+0x185ed2) [0x56365a16eed2]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sas(+0x4c60c) [0x56365a03560c]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x14b) [0x7f054eb6e70b]
/lib64/libpthread.so.0(+0x12cf0) [0x7f055042acf0]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sasmetas(addForKeys+0x1f0) [0x7f0506769af0]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sasmetas(addmeta+0x329) [0x7f0506743559]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sasmetas(refmeta+0x1246) [0x7f050673eb36]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sasmetas(sasmetas+0x2d10) [0x7f05067321c0]
/app/sas/software/SASHome/SASFoundation/9.4/sasexe/sas(+0x4c1eb) [0x56365a0351eb]
/lib64/libpthread.so.0(+0x81ca) [0x7f05504201ca]
/lib64/libc.so.6(clone+0x43) [0x7f054f8dce73]
NOTE: The SAS System stopped processing this step because of errors.
The following behavior has been observed when a DB2 table contains more than one foreign key:
- PROC METADATA registers tables until it reaches the problematic table
- The registered metadata is not complete. For example, if the DB2 table has indexes, they are not registered.
- PROC METADATA stops processing any further tables.
The only workaround is to exclude tables that contain more than one foreign key and register the tables manually.
Click the Hot Fix tab in this note to access the hot fix for this issue.
After you install the hot fix, multiple foreign keys are ignored, a note similar to the following is written to the SAS log, and further tables are processed as normal.
NOTE: Unable to register foreign keys for table <table name> due to multiple keys.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | Base SAS | z/OS | 9.4_M8 | 9.4 TS1M8 | ||
| z/OS 64-bit | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft® Windows® for x64 | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows 8 Enterprise 32-bit | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows 8 Enterprise x64 | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows 8 Pro 32-bit | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows 8 Pro x64 | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows 8.1 Enterprise x64 | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows 8.1 Pro 32-bit | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows 8.1 Pro x64 | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows 10 | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows 11 | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows Server 2008 | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows Server 2008 R2 | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows Server 2008 for x64 | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows Server 2012 Datacenter | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows Server 2012 R2 Std | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows Server 2012 Std | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows Server 2016 | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows Server 2019 | 9.4_M8 | 9.4 TS1M8 | ||||
| Microsoft Windows Server 2022 | 9.4_M8 | 9.4 TS1M8 | ||||
| Windows 7 Enterprise 32 bit | 9.4_M8 | 9.4 TS1M8 | ||||
| Windows 7 Enterprise x64 | 9.4_M8 | 9.4 TS1M8 | ||||
| Windows 7 Home Premium 32 bit | 9.4_M8 | 9.4 TS1M8 | ||||
| Windows 7 Home Premium x64 | 9.4_M8 | 9.4 TS1M8 | ||||
| Windows 7 Professional 32 bit | 9.4_M8 | 9.4 TS1M8 | ||||
| Windows 7 Professional x64 | 9.4_M8 | 9.4 TS1M8 | ||||
| Windows 7 Ultimate 32 bit | 9.4_M8 | 9.4 TS1M8 | ||||
| Windows 7 Ultimate x64 | 9.4_M8 | 9.4 TS1M8 | ||||
| 64-bit Enabled AIX | 9.4_M8 | 9.4 TS1M8 | ||||
| 64-bit Enabled Solaris | 9.4_M8 | 9.4 TS1M8 | ||||
| HP-UX IPF | 9.4_M8 | 9.4 TS1M8 | ||||
| Linux for x64 | 9.4_M8 | 9.4 TS1M8 | ||||
| Solaris for x64 | 9.4_M8 | 9.4 TS1M8 | ||||
A fix for this issue for Base SAS 9.4_M8 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/L8X.html#70582
A segmentation violation occurs when you use PROC METALIB to attempt to register or update the SAS metadata for DB2 tables with foreign keys.
| Type: | Problem Note |
| Priority: | high |
| Topic: | Data Management ==> Data Sources ==> External Databases ==> DB2 Data Management ==> Data Sources ==> Metadata |
| Date Modified: | 2024-01-16 15:13:08 |
| Date Created: | 2023-12-20 03:32:42 |