If you define a library in SAS^® Management Console that uses a third party ODBC driver to access data that originates from an Adabas database management system (DBMS), and you run the METALIB procedure to update table metadata for this library, you might receive an error similar to the following:

ERROR:  Read Access Violation In Task [ METALIB (2) ]
Exception occurred at (032D5E94)
Task Traceback
Address   Frame     (DBGHELP API Version 4.0 rev 5)
032D5E94  0390F6BC  sasmetas:mcn_main+0x14E94
032D6609  0390F764  sasmetas:mcn_main+0x15609
032CEA4D  0390F9D4  sasmetas:mcn_main+0xDA4D
032CC8A2  0390FBE0  sasmetas:mcn_main+0xB8A2
032C23A3  0390FF8C  sasmetas:mcn_main+0x13A3
00F22B02  0390FFA4  sashost:Main+0xBE72
00F26C20  0390FFB8  sashost:Main+0xFF90
77E6608B  0390FFEC  kernel32:GetModuleFileNameA+0xEB

PROC METALIB uses the column sequence number that is returned from the database as an internal column list index. Because most databases start the column sequence number at 1, PROC METALIB expects the first sequence number it receives to be 1. However, the Adabas DBMS begins its column sequence numbering at 0. As a result PROC METALIB is not able to successfully build the internal column list index.

Select the Hot Fix tab in this note to access the hot fix for this issue.

In addition to installing the hot fix, in order to completely solve this problem you must also create the META_ADABAS environment variable in your operating system and set the value of this variable to 1.

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at: