CHECK pending status

This topic describes how CHECK PLUS sets and resets CHECK pending (CHKP) status.

Objects that are in CHKP status

For a Db2 object that is in CHKP status, CHECK PLUS determines whether to reset the status:

• If CHECK PLUS finds no Db2 defined RI violations or check constraint violations in the object, CHECK PLUS resets the CHKP status for each checked space, partition.

• If CHECK PLUS finds Db2 defined RI violations or check constraint violations, the utility leaves the CHKP status unchanged.

  Tip

  If you add a constraint that causes the space to be put in CHKP status and you know that this constraint is the only one that you need to check to verify integrity, use a constraint list to limit the checking to that specific constraint.

  Important

  When you use the CONSTRAINT option, CHECK PLUS resets the CHKP status if it finds no violations of the specified constraints, regardless of the status of the unchecked constraints.

Objects that are not in CHKP status

For a Db2 object that is not in CHKP status, CHECK PLUS sets the CHKP status for the object if the utility finds Db2-defined RI violations or check constraint violations in the object.

Additional information about CHKP status

The Db2 CHKP status is independent of user-defined RI rules, user-defined column constraints, and violations of either. CHECK PLUS does not use CHKP statuses or the CHECKRID and CHECKFLAG values in the Db2 catalog for user-defined RI. For more information, see User-defined RI.

If you use ACKESQL (the program that CHECK PLUS provides) to delete rows with constraint violations, you can establish options to reset CHKP status during execution of ACKESQL. For more information, see Reset/lock parameter.