Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

RECOVER CATALOG TO REPLICATION

The database administrator can use the utility statement RECOVER CATALOG TO REPLICATION to reset an entire original database with a complete replication to the status of the replication.

During this process, the CAT-REC file and the metadata are also adapted. The database administrator must save the status before RECOVER, if he/she wants to return to this status later.

When an original has been reset, all old log files are overwritten. In other words the status before the reset can no longer be reached with RECOVER.

If you use the COPY function, the replication is retained and can be used for further processing. If you use the RENAME function, the replication becomes the original and is no longer available as a replication. Replication and original must be located on the DBH user ID and the files of the original must no longer exist as otherwise you cannot recatalog the files.

If a partial replication is used, only the spaces contained in the partial replication are reset. These are the catalog space and the user spaces which are current in the partial replication. All other user spaces of the original must then be adjusted to the reset state. In the case of NO LOG index spaces, this can take place automatically by means of RECOVER CATALOG TO REPLICATION by specifying GENERATE INDEX ON NO LOG INDEX SPACE. All other spaces must be adjusted individually with RECOVER SPACE.