Roll-Forward

Click on this check box to perform roll-forward recovery. 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 database or database partition.

Note:

If you need to restore a single database partition, you can perform roll-forward recovery to the end of the logs to bring it up to the same level as the other database partitions in the database.

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 all table spaces is checked. The date and time of the table space that has already been rolled forward to the most recent date and time (if any) is displayed.

Note:

In a partitioned database environment, the database is located across many nodes. In this environment, if you are performing point-in-time roll-forward recovery, all database partitions must be rolled forward to ensure that all partitions are at the same level.

• Use the Date field to specify the date to which you want to roll forward.

  You can either type the date, or you can click on the arrow to open a calendar on which you select the date. Click on the arrows at the top of the calendar to display the month that you want, then on a date to select it. The calendar closes, and the date you selected will be displayed in the field.

• Use the Time field to specify the time to which you want to roll forward. To change the time, click on the portion of the time that you want to change and either type the value that you want, or use the up and down arrows to adjust the value.

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

[ DB2 List of Books | Search the DB2 Books ]