Problem Note 63593: The METALIB procedure might fail with a segmentation violation or an error when you update tables that contain multiple foreign keys
 |  |  |  |  |
When you use PROC METALIB or the Update Table Metadata menu selection in SAS® Management Console, the update process might fail to complete successfully. This problem occurs when the following conditions are true:
- The table that you are trying to update contains multiple foreign keys.
- You have installed Hot Fix B6Q042.
When this problem occurs, you see messages similar to the following in the SAS log:
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 [METALIB ]
Segmentation Violation
Segmentation Violation
Traceback of the Exception:
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sas(+0x1666ce) [0x55e13f6616ce]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sas(+0x4e7df) [0x55e13f5497df]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7ff4c3d83a44]
/lib64/libpthread.so.0(+0xf5e0) [0x7ff4c53a15e0]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sasmetas(resolveIC+0x397) [0x7ff47a78f267]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sasmetas(updmeta+0x25c8) [0x7ff47a7702a8]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sasmetas(refmeta+0x1553) [0x7ff47a76c6d3]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sasmetas(sasmetas+0x262e) [0x7ff47a76083e]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sas(vvtentr+0x18a) [0x55e13f54933a]
/lib64/libpthread.so.0(+0x7e25) [0x7ff4c5399e25]
/lib64/libc.so.6(clone+0x6d) [0x7ff4c498a34d]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sas(+0x1666ce) [0x55e13f6616ce]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sas(+0x4e7df) [0x55e13f5497df]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7ff4c3d83a44]
/lib64/libpthread.so.0(+0xf5e0) [0x7ff4c53a15e0]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sasmetas(resolveIC+0x397) [0x7ff47a78f267]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sasmetas(updmeta+0x25c8) [0x7ff47a7702a8]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sasmetas(refmeta+0x1553) [0x7ff47a76c6d3]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sasmetas(sasmetas+0x262e) [0x7ff47a76083e]
/install/RiskTesting/SASHome/SASFoundation/9.4/sasexe/sas(vvtentr+0x18a) [0x55e13f54933a]
/lib64/libpthread.so.0(+0x7e25) [0x7ff4c5399e25]
/lib64/libc.so.6(clone+0x6d) [0x7ff4c498a34d]
When this problem occurs, complete the following steps to ensure that the table metadata is correct:
- Delete the tables that failed to update from the metadata.
- Register the tables again using SAS Management Console or PROC METALIB code.
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 | z/OS | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 |
| z/OS 64-bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft® Windows® for x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Enterprise 32-bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Enterprise x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Pro 32-bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8 Pro x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8.1 Enterprise x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8.1 Pro 32-bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 8.1 Pro x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows 10 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2008 | 9.4_M5 | 9.4 TS1M5 | ||||
| Microsoft Windows Server 2008 R2 | 9.4_M5 | 9.4 TS1M5 | ||||
| Microsoft Windows Server 2008 for x64 | 9.4_M5 | 9.4 TS1M5 | ||||
| Microsoft Windows Server 2012 Datacenter | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2012 R2 Std | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2012 Std | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Microsoft Windows Server 2016 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Enterprise 32 bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Enterprise x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Home Premium 32 bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Home Premium x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Professional 32 bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Professional x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Ultimate 32 bit | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Windows 7 Ultimate x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| 64-bit Enabled AIX | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| 64-bit Enabled Solaris | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| HP-UX IPF | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Linux for x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
| Solaris for x64 | 9.4_M5 | 9.4_M7 | 9.4 TS1M5 | 9.4 TS1M7 | ||
A fix for this issue for Base SAS 9.4_M6 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/D9T.html#63593A fix for this issue for Base SAS 9.4_M5 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/B6Q.html#63593
After you apply Hot Fix B6Q042, you might encounter an issue in which PROC METALIB or the Update Table Metadata menu selection in SAS® Management Console fails with a segmentation violation or an error. This problem occurs when the table that you are trying to update contains multiple foreign keys.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2019-05-16 10:43:17 |
| Date Created: | 2019-02-01 12:41:25 |