Recovery implications for objects that are not logged

You can use the RECOVER utility on objects that have the NOT LOGGED attribute. The NOT LOGGED attribute does not mean that the contents of an object are not recoverable. However, the modifications to the object that is not logged are not recoverable.

Objects that are not logged include the table space, the index, and the index space. Recovery can be to any recoverable point. A recoverable point is established when:

• A table space is altered from logged to not logged.
• When an image copy is taken against an object that is not logged.
• An ALTER TABLE statement is issued with the ADD PARTITION clause, against a table in a table space that has the NOT LOGGED attribute.
• Db2 adds a new partition in response to insertion of data into a partition-by-growth table space.

The TORBA or TOLOGPOINT keywords can also be used for a point-in-time recovery on an object that is not logged, but the RBA or LRSN must correspond to a recoverable point or message DSNU1504I is issued.

If a base table space is altered so that it is not logged, and its associated LOB table spaces already have the NOT LOGGED attribute, then the point where the table space is altered is not a recoverable point.

If Db2 restart recovery determines that a table space that is not logged might have been in the process of being updated at the time of the failure, then the table space or partition is placed in the LPL and is marked RECOVER-pending.