Removing pages from the logical page list
Although the Db2 subsystem always attempts automated recovery of logical page list (LPL) pages when the pages are added to the LPL, you can also perform manual recovery.
About this task
You can run only the following utilities on an object with pages in the LPL:
- LOAD with the REPLACE option
- MERGECOPY
- REBUILD INDEX
- RECOVER, except for:
- RECOVER…PAGE
- RECOVER…ERROR RANGE
- REPAIR with the SET statement
- REPORT
Procedure
When
an object has pages on the LPL, to manually remove those pages and
make them available for access when Db2 is running:
- Start the object with access (RW) or (RO). That command is
valid even if the table space is already started.
When you issue the START DATABASE command, message DSNI006I is displayed, indicating that LPL recovery has begun. If second pass log apply for LPL recovery starts, message DSNI051I is displayed. Message DSNI022I is displayed periodically to give you the progress of the recovery. When recovery is complete, message DSNI021I is displayed.
When you issue the START DATABASE command for a LOB table space that is defined as LOG NO, and Db2 detects that log records that are required for LPL recovery are missing due to the LOG NO attribute, the LOB table space is placed in AUXW status, and the LOB is invalidated.
- Run the RECOVER or REBUILD INDEX utility on the object.
The only exception to this is when a logical partition of a nonpartitioned index is in the LPL and has RECP status. If you want to recover the logical partition by using REBUILD INDEX with the PART keyword, you must first use the START DATABASE command to clear the LPL pages.
- Run the LOAD utility with the REPLACE option on the object.
- Issue an SQL DROP statement for the object.
