1·Rollforward to end of logs and stop
前滚到日志的最后，然后停止
2·You will see a ROLLFORWARD command complete successfully prompt.
您将看到ROLLFORWARD命令成功完成的提示。
3·On a split mirror, the catalogs will be inconsistent (until rollforward is completed).
在分割镜像上，编目将变得不一致（直到完成前滚）。
4·Therefore, rollforward through any of the logs from the source database is not possible.
因此，用源数据库中的任何日志进行前滚都是行不通的。
5·They are retrieved when the ROLLFORWARD utility needs to use them to restore a database.
当ROLLFORWARD实用程序需要使用日志文件来恢复数据库时，就会检索它们。
6·overflowlogpath (default: NULL) - Indicates the log path to use during rollforward recovery.
overflowlogpath（默认值是 NULL）—— 表示在前滚恢复期间使用的日志路径。
7·Once you have created the standby database, do not use the ROLLFORWARD DATABASE command as a recovery option.
创建备用数据库之后，不要使用 ROLLFORWARD DATABASE 命令作为恢复选项。
8·This can be done by issuing the db2 rollforward command with the stop or complete parameter to bring the database into a consistent state.
这可以通过带stop或complete参数发出db 2 rollforward命令，从而将数据库带到一致(consistent)状态来实现。
9·No crash recovery is initiated, and the database remains inconsistent until a rollforward to the end of logs and stop/complete has been issued.
这里不会进行崩溃恢复，并且数据库将处于不一致状态，直到前滚到日志的最后并发出了 stop/complete。
10·The second restores to the most recent state, using a combination of full backup plus rolling forward the transaction log, called rollforward recovery.
另一种机制通过使用全备份，并前滚事务日志，使数据库恢复到最近的状态，这种机制也叫前滚恢复。