"Check pending" problems: DB2® database load utility

"Check pending" problems can occur when using a DB2® database load utility with IBM® Campaign. Use the following suggestions to help troubleshoot these types of issues.

Symptoms

You get a SQL0668N error.

Causes

If a database loader is used to insert records in a table and the table has referential constraints, the table will be left in a "check pending" state after the load operation. Referential constraints include unique constraints, range constraints for partitioned tables, generated columns, and LBAC security rules. When a table is in this state, you get a SQL0668N error if any select query is performed on the table.

Resolving the problem

To get the table out of a "check pending" state, run the following command:

SET INTEGRITY FOR TABLE <TABLENAME> IMMEDIATE CHECKED

The following code can be used in the script:

load client from <DATAFILE> of del modified by coldel| insert into <TABLE>(
 <FIELDNAME><,>
 ) 
nonrecoverable;
 set integrity for <TABLE> immediate checked;