The following error message can be issued when you attempt to register very large DB2 tables in metadata:

ERROR: CLI cursor fetch error: [IBM][CLI Driver][DB2/AIX64] SQL0413N
Overflow occurred during numeric data type conversion. SQLSTATE=22003

The DB2 API does not support BIGINT data type for CARDINALITY columns and therefore, SAS/ACCESS^® Interface to DB2 is not able to support it either. Currently in the DB2 API, CARDINALITY is defined as an INTEGER and if a very large table is used the above error is received. For example, a table with over 6 billion rows in an index can cause the error above when SAS tries to query the information about the index.

This issue occurs outside of SAS using the DB2 command-line processor as well.

To work around this issue:

• Drop the indexes on the DB2 table outside of SAS, import the large table into metadata within SAS, and then recreate the indexes on the DB2 table outside of SAS.
• Create a duplicate of the original table without any rows and call it 'dummy' outside of SAS. Rename the original table to 'old' outside of SAS. Now rename the dummy table to the original table outside of SAS. Import the table, which is really just the dummy (empty) table with same metadata within SAS. Then finally rename the old table back to the original table outside of SAS.

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

Operating System and Release Information

A fix for this issue for SAS/ACCESS Interface to DB2 9.21_M2 is available at: