Recovery of table spaces

The way that you recover DB2® table spaces depends on several factors, including the type of table space that needs recovery.

When you recover table spaces to a prior point of consistency, you need to consider:

How partitioned table spaces, segmented table spaces, LOB table spaces, XML table spaces, and table space sets can restrict recovery.
If you take system-level backups, how certain utility events can prohibit recovery to a prior point in time.

Recovery of partitioned table spaces
Recovering partitioned table spaces to a point in time has several limitations.
Recovery of segmented table spaces
You can restore data on a segmented table space to a prior point in time. When you do this, information in the database descriptor (DBD) for the table space might not match the restored table space.
Recovery of LOB table spaces
When you recover tables with LOB columns, recover the entire set of objects. The entire set of objects includes the base table space, the LOB table spaces, and index spaces for the auxiliary indexes.
Recovery of XML table spaces
At times, recovering database objects to a prior point in time is necessary. When this type of recovery is needed, all related objects (including XML objects) must be recovered to a consistent point in time.
Recovery of table space sets
If you restore a page set to a prior state, restore all related tables and indexes to the same point to avoid inconsistencies.
Recovery of partition-by-growth table spaces
The RECOVER utility supports both table space-level and partition-level recovery on a partition-by-growth table space.

Parent topic: Recovery of data to a prior point in time

Related reference: