If you run PROC METALIB on a library that refers to a relational database, the procedure may fail to analyze all the tables in the library.

This problem occurs when one or more tables in the RDBMS schema contains a column that is defined with a data type that the SAS® System does not recognize, such as the TIMESTAMP data type in Oracle.

When you run PROC METALIB on such a library, you will see notes similar to the following in the log:

   WARNING: This variable has been dropped.
   NOTE: A total of 28 tables were analyzed for library "Oracle - Group 1".
   NOTE: NOEXEC statement in effect.  No Metadata changes applied.
   NOTE: Metadata for 0 tables would have been updated.
   NOTE: Metadata for 0 tables would have been deleted.
   NOTE: Metadata for 18 tables would have been added.
   NOTE: Metadata for 10 tables matched the data sources.
   NOTE: 0 other tables were not processed due to error or UPDATE_RULE.
   NOTE: The following 1 column(s) in DATALIB.BATCH_DETAIL_DATA  have been   
         automatically dropped because they have a datatype that is not  
         supported by this engine:
         BDD_INFO_DATE 

In this situation, the number of tables reported in the first note is less than the total number of tables in the entire library.

The only circumvention for this problem is to use the SELECT or EXCLUDE statement in PROC METALIB to selectively include or exclude tables and views in groups that prevent the offending columns from interfering with the metadata import.

Operating System and Release Information