The database administrator can extend a replication by adding the specified user spaces to a replication using the utility statement REFRESH SPACE. These spaces can be new to the replication. They may also have previously belonged to the replication (“previous replication spaces”), but were then deleted from the replication because logging was interrupted or because they were invalid.
REFRESH SPACE adds the specified spaces from a SESAM backup copy (disk or magnetic tape cartridge) or a foreign copy to the replication and updates it to the current state of the replication by applying the modifications logged in the logging files.
REFRESH SPACE does not check whether specified spaces are already contained in the replication. Spaces that already exist are overwritten. If a replication space is recreated, the medium of the replication catalog space will be used.
The replication must be updated for REFRESH SPACE to such an extent that the backups used are known in the replication. Backups that were created at a time before the backup from which the replication was created can also be used.
If several spaces are specified in REFRESH SPACE, all the backups must have the same time stamp.
Modifications logged in the logging files are applied to spaces by REFRESH SPACE to update them to the current state of the replication. Logging must not have been interrupted between the backup used and the state of the replication on the affected spaces in the original.
The database administrator must make available all the DA-LOG files that were created from the time of the backup to the current state of the replication. You can determine which files are required via the RECOVERY_UNITS in the INFORMATION_SCHEMA.