Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Updating and extending replications

The database administrator can use the REFRESH REPLICATION utility statement to update a replication or a partial replication:

  • REFRESH REPLICATION
    updates the whole replication or partial replication by applying the modifications logged in the logging files.

  • REFRESH REPLICATION FOR SPACE
    only updates the specified spaces and the catalog space of the replication by applying the modifications logged in the logging files. The replication will then only contain these spaces and will become a partial replication.

A replication should be updated in the following cases:

  • If a recovery application needs access to the most recent values.

  • If the replication is to be used as a shadow database to allow particularly fast repair.

The database administrator can extend a replication by adding user spaces of the original to the replication using the utility statement REFRESH SPACE on the basis of a backup. These spaces can be new to the replication or they may have previously belonged to the replication (“previous replication spaces”). The replication must be updated to such an extent that the backup is known in the metadata of the replication.
You can find information about current and previous replication spaces via the utility monitor, mask COP.4.6 (see “Utility Monitor” manual).

During REFRESH REPLICATION or REFRESH SPACE, read applications cannot access the replication, since exclusive access is necessary for the update process. The replication may be added only to the SQL database catalog of the DBH for which the utility statement has been executed.