Recovery of pages on the logical page list

Db2 attempts to automatically recover pages when they are added to the logical page list. Recovered pages are deleted from the logical page list when recovery processing successfully completes.

In some situations—such as a channel failure between the group buffer pool and the processor, a transient disk problem, or Db2 in restart—the automatic LPL recovery processor cannot be initiated, or the recovery cannot complete. In these situations, the pages are kept in the logical page list. The following tasks show several ways to perform manual LPL recovery:
  • Start the object with access (RW) or (RO). This command is valid even if the table space is already started.

    When you issue the command START DATABASE, Db2 issues messages to indicate the status of the recovery, including:

    • DSNI005I, which indicates an error
    • DSNI006I, which indicates the start of recovery
    • DSNI021I, which indicates successful completion
    • DSNI022I, which provides the status of recovery operations
    • DSNI051I, which indicates that second pass log apply has started
  • Run the RECOVER utility on the object.

    The only exception to this is when a logical partition of a type 2 nonpartitioned index has both LPL and RECP status. If you want to recover the logical partition using RECOVER INDEX with the PART keyword, you must first use the command START DATABASE to clear the logical page list pages.

  • Run the LOAD utility with the REPLACE option on the object.
  • Issue an SQL DROP statement for the object.
  • Use the utility REPAIR SET with NORCVRPEND. This can leave your data in an inconsistent state.
  • Use START DATABASE ACCESS(FORCE). This can leave your data in an inconsistent state.

None of the items in the preceding list work if retained locks are held on the object. You must restart any failed member that is holding those locks.

When a table space or partition is placed in the LPL because undo processing is needed for a NOT LOGGED table space, either at restart time or during rollback processing, automatic LPL recovery is not initiated. A -START DATABASE command identifying this table space will have no effect on the LPL status