Continuing a stopped or failed rollforward operation
You can continue a rollforward operation if any of the following occurred: the previous rollforward failed; the previous rollforward was interrupted; or the previous rollforward finished, but the command did not specify either STOP or COMPLETE.
Before you begin
You should not be connected to the database that is to be rollforward recovered. The rollforward utility automatically establishes a connection to the specified database, and this connection is terminated at the completion of the rollforward operation.
About this task
One option you have when continuing a rollforward operation is to use a forced stop, which you do by issuing a ROLLFORWARD DATABASE command with the STOP option, but specifying TO. A forced stop means that the rollforward utility ignores certain errors if they are safe to ignore. For example, missing log file errors, checksum errors, log chain errors, and not reaching the point in time are considered ignorable errors. If Db2® determines that it is safe to stop, then the rollforward operation goes through the undo phase, and the database will be available for normal connections. If Db2 determines that it is not safe to stop, then the rollforward operation fails and the database remains in rollforward pending state.
Restrictions
- a rollforward to the same point in time
- a rollforward to a later point in time
- a rollforward to the end of logs
- a rollforward with the STOP or COMPLETE option, but without a point-in-time, END OF LOGS, or END OF BACKUP option
Procedure
To continue a rollforward operation, use the following steps: