RDE maintenance at database recovery

When you recover the database to the state that is defined by the current DBD, Integrity Checker verifies the DMB by using the latest DMB information.

When you recover the database to the state before a DBD change with a time stamp recovery, Integrity Checker verifies the DMB by using the DMB information that was used when the database backup was created. Therefore, you must restore the RDE that contains the DMB information that was used when the backup was created.

If you use one of the following tools to recover the database, Integrity Checker automatically restores the RDE that was used when the backup was created:

• IMS High Performance Image Copy
• IMS Database Recovery Facility of IMS Recovery Solution Pack

However, to have Integrity Checker automatically restore the RDE, both of the following requirements must be satisfied:

• Global option module specifies that historical copies of RDEs are kept (GENMAX=1 or higher).
• The RDE that was used when the backup was created is stored in the LICON data set as an expired RDE.

If the expired RDE does not exist, use the INIT.DB command to manually create an RDE that contains the DMB information that was used before the DBD change.

When you run a time stamp recovery at a Remote Site Recovery (RSR) active site, you must recover the correct RDE at the RSR tracking site before running a recovery job at the RSR tracking site.