CHECK-pending status

The CHECK-pending (CHKP) restrictive status indicates that an object might be in an inconsistent state and must be checked.

The following utilities set CHECK-pending status on a table space if referential integrity constraints are encountered:

LOAD with ENFORCE NO
RECOVER to a point in time
CHECK LOB

Table check violations place a table space or partition in CHECK-pending status when any of the following conditions exist:

A check constraint is defined on a populated table by using the ALTER TABLE statement, and the value of the CURRENT RULES special register is DB2.
The LOAD utility is run with CONSTRAINTS NO, and check constraints are defined on the table.
CHECK DATA is run on a table that contains violations of check constraints.
A point-in-time RECOVER introduces violations of check constraints.

An index might be placed in CHECK-pending status if you recovered an index to a specific RBA or LRSN from a copy and applied the log records, but you did not recover the table space in the same list. The CHECK-pending status can also be set on an index if you specified the table space and the index, but the recovery point in time was not a point of consistency (QUIESCE or COPY SHRLEVEL REFERENCE).

Start of change The CHECK-pending status can also affect a base table space or a LOB table space. CHECK-pending status for an XML table space is set only if a new XML schema for an XML type modifier was added or removed. End of change

DB2 ignores informational referential integrity constraints and does not set CHECK-pending status for them.

The following table lists the actions to take to reset the CHECK-pending status.

Table 1. Resetting CHECK-pending status
Status	Abbreviation	Object affected	Corrective action
CHECK-pending	CHKP	Table space, base table space	Run the CHECK DATA utility. If a table space is in both REORG-pending and CHECK-pending status (or auxiliary CHECK-pending status), run the REORG TABLESPACE utility first and then run CHECK DATA to reset the respective states.
CHECK-pending	CHKP	Partitioning index, nonpartitioning index, index, XML index on the auxiliary table	Run the CHECK INDEX utility on the index. If any errors are found, use the REBUILD INDEX utility to rebuild the index from existing data.
CHECK-pending	CHKP	LOB table space	Run the CHECK LOB utility to check the LOB table space. If any errors are found, take the following actions: Correct any defects that are found in the LOB table space by using the REPAIR utility. Run CHECK LOB again to reset the CHECK-pending status. If the table space is in auxiliary warning (AUXW) status, take the actions in Auxiliary warning status .
CHECK-pending	CHKP	XML table space	Run CHECK DATA to check the XML table space. If any errors are found, take the following actions: Correct any defects that are found in the XML table space by using the REPAIR utility. Run CHECK DATA again to reset the CHECK-pending status.