Restart-pending status

Restart-pending status indicates that an object has backout work pending at the end of a Db2 restart. Backout activity against the objects must be completed.

Start of changeIn a non-data-sharing environment, objects with backout work pending are set to restart-pending (RESTP) restrictive status. In a data-sharing environment, these objects are set to advisory restart-pending (AREST) statusEnd of change

Objects in RESTP status are unavailable. You cannot use LOAD REPLACE on an object that is in the RESTP status. You also cannot run any utilities against page sets or partitions with RESTP status. Any attempt to access a page set or partition with RESTP status terminates with return code 8.

Start of changeUtilities are not restricted by the AREST status, but any write claims that are held by postponed-abort units of recovery (URs) on the objects in AREST status prevent draining utilities from accessing that page set. End of change

To reset restart-pending status, take the actions that are described in the following table.

Table 1. Resetting restart-pending status
Status Abbreviation Object affected Corrective action
Restart- pending RESTP Table space, table space partitions, index spaces, and physical index space partitions
Perform one of the following actions:
  • Use the RECOVER POSTPONED command.
  • Restart the Db2 subsystem with the LBACKOUT subsystem parameter set to AUTO.

Delay running REORG TABLESPACE SHRLEVEL CHANGE until all RESTP statuses are reset.
Start of changeAdvisory restart-pendingEnd of change AREST Table space, table space partitions, index spaces, and physical index space partitions Use the same actions that are described in the preceding row.