IBM Books

Roll-Forward

Click on this check box to perform roll-forward recovery on the table space or table space partition. There are two types of roll-forward recovery:

Roll-Forward to the end of the logs
This is the default. All changes recorded in the logs are applied to the table space.
Note: Graphic denoting partitioned database environments appears here. If you need to restore a table space partition on a specific database partition you can perform roll-forward recovery on it to the end of the logs to bring it up to the same level as the table space on the other nodes.

Roll-Forward to a point in time
Changes are rolled forward to a specific date and time. If you decide not to specify a date and time, the default is the current date and time. The Next transaction to reapply field displays the date and time of the next transaction that will be reapplied by the roll-forward operation. To determine this date and time, the roll-forward status of the table space is checked. The date and time to which the table space already been rolled forward (if any) is displayed.

Notes:

  1. You can only perform a point-in-time operation on a table space if it contains all parts of all its tables.

  2. Graphic denoting partitioned database environments appears here. In a partitioned database environment, if you want to roll forward a table space to a point in time, you must restore the table space partition at each database partition that contains a portion of the table space, and roll forward each table space partition individually to the same point in time. This ensures that the table space is consistent at each node.

[ Top of Page | Table of Contents | Glossary | Index ]

[ DB2 List of Books | Search the DB2 Books ]