Importing DBMS tables into a SAS^® Metadata Repository via the SAS^® Management Console or PROC METALIB might fail, producing messages such as the following from the:

• SAS^® Log data displayed in a details listing in the message window

    NOTE: The SAS System stopped processing this step because of errors.
    NOTE: PROCEDURE SQL used (Total process time):
          real time           1.12 seconds
          cpu time            0.01 seconds
          
    
    
    15         PROC SQL;
    16           CONNECT TO DB2( USER=dbmsuser  PASSWORD=XXXXXXXX  Datasrc=DATASOURCENAME );
    17           CREATE TABLE _ForeignKeys AS
    18           SELECT PKCOLUMN_NAME, FKTABLE_NAME, FKCOLUMN_NAME
    19           FROM CONNECTION TO DB2(DBMS::ForeignKeys("","'PSRREG#'","ADMIN_GROUP_CODES", "",
    19       ! "", ""))
    20         QUIT;
    ERROR: The following columns were not found in the contributing tables: FKCOLUMN_NAME, 
           FKTABLE_NAME, PKCOLUMN_NAME.

• SAS Log data from the SAS session running PROC METALIB

    NOTE 49-169: The meaning of an identifier after a quoted string may change in a future SAS 
                 release.  Inserting white space between a quoted string and the succeeding 
                 identifier is recommended.
    ERROR 22-7: Invalid option name XXXX.
    ERROR 22-7: Invalid option name XXXX.
    ERROR 22-7: Invalid option name XXXX.
    ERROR: Libname Libref is not assigned.
    ERROR: Libname Libref is not assigned.
    ERROR: Libname Libref is not assigned.
    
    Invalid free() attempt to deleted pool
    Traceback
    SASTBTraceBackCtx has been called with a
    string ("vacrash") instead of a CONTEXT pointer.
    Address   Frame     (DBGHELP API Version 4.0 rev 5)
    000000004B50CDA0  000000000AD80520  0001:000000000006ADA0 tkmk.dll

The problem occurs when SAS passes a query to the DBMS ForeignKeys table for the columns PKCOLUMN_NAME, FKTABLE_NAME, and FKCOLUMN_NAME, and the database client fails to return those columns. Typically, columns of other names are returned, such as:

    PKTABLE_QUALIFIER char(128)
    PKTABLE_OWNER char(128)
    _ char(128)
    _0 char(128)
    FKTABLE_QUALIFIER char(128)
    FKTABLE_OWNER char(128)
    _1 char(128)
    _2 char(128)
    _3 num

This problem has occurred with several databases, including DB2 and Sybase. The problem appears to be a result of the configuration of the DBMS client such that it returns columns of different names than SAS expects. Your database administrator should contact the DBMS client vendor for further assistance in correcting this problem.

To determine which columns are being returned to SAS, you can submit a query for all ForeignKeys columns, then look at the columns and attributes returned. For example:

The code should be submitted to the machine on which the table import or PROC METALIB is being run. The output of the DESCRIBE statement is written to the SAS Log. The output from DESCRIBE must contain the columns that SAS Management Console and PROC METALIB are expecting, i.e. PKCOLUMN_NAME, FKTABLE_NAME, and FKCOLUMN_NAME.

Operating System and Release Information