After running RESTORE SYSTEM

After you run the RESTORE SYSTEM utility, you must complete some cleanup actions, including resolving any restrictive states that were set by the utility.

Start of change

Effects of running RESTORE SYSTEM

RESTORE SYSTEM might leave objects in one of the following restrictive states:

RECOVER-pending status
A table space or partition is placed in RECOVER-pending status if any of the following events occurred after the point in the log where RESTORE SYSTEM begins log apply processing:
  • A NOT LOGGED table space was updated
  • A LOG NO utility event occurred on the table space or partition

The log point where log apply processing begins is listed in the DSNJU004 utility output as the RBLP value, or recovery base log point. See System-level backup information.

REBUILD-pending status
An index is placed in REBUILD-pending status in any of the of the following situations:
  • The index has gone through the two-pass group buffer pool RECOVER-pending (GRECP) or logical page list (LPL) recovery earlier.
  • The index is in GRECP or LPL status, and the compensation log records are written before the physical undo logs.
  • A LOG NO utility event occurred on the index after the point in the log where RESTORE SYSTEM begins log apply processing.
Related information:
End of change

After running RESTORE SYSTEM

Complete the following steps after running RESTORE SYSTEM:
  1. Stop and start each Db2 subsystem or member to remove it from access maintenance mode.
  2. Use the DISPLAY UTIL command to see if any utilities are running. If other utilities are running, use the TERM UTIL command to end them.
  3. Use the RECOVER utility to recover all objects in RECOVER-pending (RECP) or REBUILD-pending (RBDP) status, or use the REBUILD INDEX utility to rebuild objects. If a CREATE TABLESPACE, CREATE INDEX, or data set extension has failed, you can also recover or rebuild any objects in the logical page list (LPL).