这两个参数中的任何一个都足以允许前滚恢复方法。
Either of the two parameters is sufficient to allow the roll-forward recovery method.
这两个参数中的任何一个都足以允许前滚恢复方法。
Either one of the two parameters is sufficient to allow the roll-forward recovery method.
Recovery—表示保留日志，且可以用于前滚恢复。
Recovery - to indicate that the logs are retained, and can be used for forward recovery.
要在DB 2UD b中执行前滚恢复，必须使用归档日志记录。
To do a roll forward recovery in DB2 UDB, archive logging must be used.
执行前滚恢复操作的结果与使用HADR在备用数据库上重播日志的结果略有不同。
The results of performing a roll-forward recovery operation could differ slightly from replaying the logs on the standby database using HADR.
如果取消选择这两个参数，就不能对数据库进行前滚恢复，因为将不再保留日志。
If both of these parameters are de-selected, roll-forward recovery becomes unavailable for the database because logs will no longer be retained.
通过将它设置成“RECOVERY”来启用它，从而允许数据库管理器使用前滚恢复方法。
Enabling it by setting it to "recovery" allows the database manager to use the roll-forward recovery method.
另一种机制通过使用全备份，并前滚事务日志，使数据库恢复到最近的状态，这种机制也叫前滚恢复。
The second restores to the most recent state, using a combination of full backup plus rolling forward the transaction log, called rollforward recovery.
overflowlogpath（默认值是NULL）——表示在前滚恢复期间使用的日志路径。
overflowlogpath (default: NULL) - Indicates the log path to use during rollforward recovery.
如果将数据库配置成进行前滚恢复，那么就不会将当前存储在数据库日志路径目录中的归档日志移到新的位置。
Archive logs that are currently stored in the database log path directory are not moved to the new location if the database is configured for roll-forward recovery.
当使用userexit配置参数或logretain配置参数以允许前滚恢复时，活动日志路径非常重要。
The active log path is important when using either the userexit configuration parameter or the logretain configuration parameter to allow roll-forward recovery.
因为您可以更改日志路径位置，所以前滚恢复所需的日志可能会在不同的目录中或在不同的设备上存在。
Because you can change the log path location, the logs needed for roll-forward recovery may exist in different directories or on different devices.
如果您对现有数据库启用前滚恢复，将主日志的数量更改成当前正在使用的主日志和辅助日志的数量总和，再加1。
If you are enabling an existing database for roll-forward recovery, change the number of primary logs to the sum of the number of primary and secondary logs you are currently using, plus 1.
对于为了前滚恢复而在数据库中启用long varchar和LOB字段这样的附加信息，也会记录在日志中。
Additional information is logged for long varchar and LOB fields in a database enabled for roll-forward recovery.
如果您选择使用归档日志记录，并执行联机备份和前滚恢复，那么您可以恢复到数据丢失最少的那个时间点，或者恢复到结束日志的时候。
If you choose to have archive logging, and do an online backup and roll forward recovery, you can recover to a point in time or to the end of the logs for the minimum loss of data.
该策略不应该用在线事务处理(on - line transaction processing,OLTP)环境，因为它不可能进行前滚恢复。
This strategy should not be a choice in an on-line transaction processing (OLTP) environment since roll-forward recovery is not possible. Figure 1 below illustrates circular logging.
如果logretain设置成“Recovery”或者userexit设置成“Yes”(请参阅下一节)，将保留活动日志文件，而且这些文件将变成联机归档日志文件，以便在前滚恢复中使用。
If logretain is set to "recovery" or userexit is set to "Yes" (see below), the active log files will be retained and become online archive log files for use in roll-forward recovery.
注意，您可以手动恢复完全备份，应用星期六的增量备份映像并进行前滚。
Note that you can restore either a full backup manually, apply the Saturday incremental backup image and roll forward.
两种数据库都提供了前滚到某个时间点以及前滚到日志的结束的恢复。
Both databases provide the roll forward until a certain point in time and to the end of the logs.
不完全恢复是这样的一种恢复，该恢复包括前滚重做日志，以便数据库恢复到某个时间戳，该前滚操作允许您丢失一些数据。
An incomplete recovery is a recovery that involves rolling forward the redo logs to bring the database to timestamp as far as the roll forward allows you with some lost of data.
在CLP中，您将发出下面的命令来执行恢复，并前滚整个数据库。
In the CLP, you will issue the following commands to do a restore and roll forward a full database.
要恢复增量备份，只需要两步，恢复增量数据库并前滚。
To recover from the incremental backup, there are only two steps to follow, Restore the incremental database and roll forward to completion.
使用完全恢复将被删除表前滚至e:\tmp。
Roll forward using complete recover dropped table to e:\tmp.
在DB 2UDB和Oracle中，这些失败的处理方式大致是一样的，都是通过脱机或联机备份并使用前滚操作恢复日志来完成的。
These failures are handled much the same way in DB2 UDB and Oracle, by restoring either offline or online backups and using roll forward operations to recover the logs.
在CLP中，可以发出以下命令来执行恢复，并前滚表空间。
In the CLP, you will issue the following to do a restore and roll forward a table space.
这里不会进行崩溃恢复，并且数据库将处于不一致状态，直到前滚到日志的最后并发出了stop/complete。
No crash recovery is initiated, and the database remains inconsistent until a rollforward to the end of logs and stop/complete has been issued.
对于相同场景中的delta备份和恢复，您将恢复每天的delta备份映像(星期一到星期六)，并执行前滚操作来完成恢复。
For delta backup and restore, in the same scenario, you will restore each day's delta backup image (Monday through Saturday) and roll forward to complete the recovery.
可以只进行恢复而不进行前滚。
此进程在回滚、重启恢复和前滚期间读取日志文件。
This process reads log files during rollback, restart recovery and roll forward.
要进行恢复，而又不丢失数据，那么您需要从第一个星期天备份恢复，然后恢复星期六取得的增量备份并进行前滚。
To restore without losing data, you will restore from the first Sunday backup, followed by incremental backup taken on Saturday and roll forward.
应用推荐