Problem Note 39550: A Read access violation occurs when you use the METALIB procedure to import or register database tables into the SAS® Metadata Repository
The METALIB procedure enables you to import or register tables from a SAS library or a database library into the SAS Metadata Repository. This procedure provides a programmatic approach to import or register tables as an alternative to doing this task manually via SAS® Management Console. As is the case when you manually import tables, PROC METALIB stores metadata about the physical tables. The procedure does not store the underlying data tables in the SAS Metadata Repository.
When the database table contains an index that is created by an expression rather than from a physical column, PROC METALIB generates the following Read access violation:
For example, this statement creates an index from an expression rather than a physical column in a database table:
create index IDXNAME on STUDENTS (UPPER ("NAME"))
In this example, UPPER ("NAME") is not an actual column. The database references this expression as an internal name, such as SYS_NC00008$. PROC METALIB fails to pair the index column with a physical column in the database because SYS_NC00008$ is not a physical column, and the Read access violation occurs.
There is not a workaround for this issue.
Operating System and Release Information
SAS Metadata Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Datacenter Server
Microsoft Windows 2000 Server
Microsoft Windows 2000 Professional
Microsoft Windows NT Workstation
Microsoft Windows Server 2003 Datacenter Edition
Microsoft Windows Server 2003 Enterprise Edition
Microsoft Windows Server 2003 Standard Edition
Microsoft Windows XP Professional
64-bit Enabled AIX
64-bit Enabled Solaris
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at: