CHECK-pending status

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

The following situations are examples of when CHKP status is set:

  • The following utilities set CHKP status on a table space if referential integrity constraints are encountered:
    • LOAD with ENFORCE NO
    • RECOVER for a point-in-time recovery
    • CHECK LOB
    • REORG DISCARD
    Db2 ignores informational referential integrity constraints and does not set CHKP status for them.
  • A table space or partition is placed in CHKP status in any of the following situations that might introduce table check violations:
    • 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 ENFORCE NO, and check constraints are defined on the table.
    • The CHECK DATA utility is run on a table that contains violations of check constraints.
    • A point-in-time recovery introduces violations of check constraints.
  • An index might be placed in CHKP status in the following recovery situations:
    • An index was recovered to a specific RBA or LRSN based on a copy and then applying log records, but the table space was not recovered in the same list.
    • A table space and index were recovered, but the recovery point in time was not a point of consistency. (A point of consistency is established by running the QUIESCE utility or the COPY utility with SHRLEVEL REFERENCE.)
  • CHKP status for an XML table space is set only if a new XML schema for an XML type modifier was added or removed.

To reset CHKP status, take the actions that are described in the following table.

Table 1. Resetting CHECK-pending status
Status Abbreviation Object affected Corrective action
CHECK-pending CHKP Table space or base table space Run CHECK DATA. See Resetting CHECK-pending status.

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. See Resetting CHECK-pending status for a LOB table space.

CHECK-pending CHKP XML table space

Run CHECK DATA to check the XML table space. If any errors are found, take the following actions:

  1. Correct any defects that are found in the XML table space by using the REPAIR utility.
  2. Run CHECK DATA again to reset the CHECK-pending status.