互联网服务
include logs在线完整备份还原时提示需要当前活动日志
在做include logs在线完整备份还原时提示需要当前活动日志，不能完成还原。请各位帮忙看看。
在用V9.5fp4版本，在A机器上，每天00.10做一个带include logs的在线完整备份，当用这个文件在B机器上还原时，报下面这段错误
2012-06-08 08:40:32 0 0 SQL1064N DB2STOP processing was successful.
SQL1064N DB2STOP processing was successful.
06/08/2012 08:40:34 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
DB20000I The DROP DATABASE command completed successfully.
DB20000I The RESTORE DATABASE command completed successfully.
SQL1265N The archive log file "S0003286.LOG" is not associated with the
current log sequence for database "UPSRVDB" on node "0".
还原时使用的语句：
db2 "restore db upsrvdb from /backup/bak144/dbbak taken at 20120608001002 LOGTARGET /home/db2inst1/DB/target"
db2 "rollforward db upsrvdb to end of backup and complete overflow log path(log path(/home/db2inst1/DB/target)"
在B机器还原只是偶尔会出现上面的错误，有时又能完成还原
A机器所使用日志信息：
First active log file = S0003285.LOG
Logs:
Current Log Number 3286
Pages Written 4738
Method 1 Archive Status Success
Method 1 Next Log to Archive 3286
A机器db2diag.log日志内容如下：
2012-06-07-14.24.10.351799+480 I96806485E369 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0003283.LOG.
2012-06-07-14.24.10.591960+480 I96806855E509 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0003283.LOG to
/backup/archive_log/db2inst1/UPSRVDB/NODE0000/C0000000/ from
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.
2012-06-07-21.56.55.103701+480 I96807365E369 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0003284.LOG.
2012-06-07-21.56.55.349423+480 I96807735E509 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0003284.LOG to
/backup/archive_log/db2inst1/UPSRVDB/NODE0000/C0000000/ from
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.
2012-06-08-00.10.02.582228+480 E96808245E496 LEVEL: Info
PID : 5193 TID : 47271529933120PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : UPSRVDB
APPHDL : 0-1505 APPID: *LOCAL.db2inst1.120607161002
AUTHID : DB2INST1
EDUID : 41347 EDUNAME: db2agent (UPSRVDB) 0
FUNCTION: DB2 UDB, database utilities, sqluxGetDegreeParallelism, probe:507
DATA #1 :
Autonomic backup/restore - using parallelism = 5.
2012-06-08-00.10.03.704933+480 E96808742E523 LEVEL: Info
PID : 5193 TID : 47271529933120PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : UPSRVDB
APPHDL : 0-1505 APPID: *LOCAL.db2inst1.120607161002
AUTHID : DB2INST1
EDUID : 41347 EDUNAME: db2agent (UPSRVDB) 0
FUNCTION: DB2 UDB, database utilities, sqluxGetAvailableHeapPages, probe:618
DATA #1 :
Autonomic BAR - heap consumption.
Targetting (50%) - 55184 of 110368 pages.
2012-06-08-00.10.03.705138+480 E96809266E510 LEVEL: Info
PID : 5193 TID : 47271529933120PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : UPSRVDB
APPHDL : 0-1505 APPID: *LOCAL.db2inst1.120607161002
AUTHID : DB2INST1
EDUID : 41347 EDUNAME: db2agent (UPSRVDB) 0
FUNCTION: DB2 UDB, database utilities, sqlubTuneBuffers, probe:869
DATA #1 :
Autonomic backup - tuning enabled.
Using buffer size = 4097, number = 5.
2012-06-08-00.10.03.979451+480 E96809777E457 LEVEL: Info
PID : 5193 TID : 47271529933120PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : UPSRVDB
APPHDL : 0-1505 APPID: *LOCAL.db2inst1.120607161002
AUTHID : DB2INST1
EDUID : 41347 EDUNAME: db2agent (UPSRVDB) 0
FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:1508
MESSAGE : Starting an online db backup.
2012-06-08-00.10.47.688427+480 I96810235E371 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0003284.LOG.
2012-06-08-00.10.47.960617+480 I96810607E450 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4148
MESSAGE : Completed retrieve for log file S0003284.LOG on chain 0 to
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.
2012-06-08-00.10.47.961117+480 I96811058E369 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0003285.LOG.
2012-06-08-00.10.51.185184+480 I96811428E509 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0003285.LOG to
/backup/archive_log/db2inst1/UPSRVDB/NODE0000/C0000000/ from
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.
2012-06-08-00.10.51.557321+480 I96811938E371 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0003283.LOG.
2012-06-08-00.10.51.931047+480 I96812310E450 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4148
MESSAGE : Completed retrieve for log file S0003283.LOG on chain 0 to
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.
2012-06-08-00.10.51.932112+480 I96812761E371 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0003282.LOG.
2012-06-08-00.10.52.168200+480 I96813133E450 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4148
MESSAGE : Completed retrieve for log file S0003282.LOG on chain 0 to
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.
2012-06-08-00.10.55.352769+480 E96813584E431 LEVEL: Info
PID : 5193 TID : 47271529933120PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : UPSRVDB
APPHDL : 0-1505 APPID: *LOCAL.db2inst1.120607161002
AUTHID : DB2INST1
EDUID : 41347 EDUNAME: db2agent (UPSRVDB) 0
FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:843
MESSAGE : Backup complete.
2012-06-08-03.20.09.606038+480 E96814016E538 LEVEL: Event
PID : 5193 TID : 47270686878016PROC : db2sysc 0
在用V9.5fp4版本，在A机器上，每天00.10做一个带include logs的在线完整备份，当用这个文件在B机器上还原时，报下面这段错误
2012-06-08 08:40:32 0 0 SQL1064N DB2STOP processing was successful.
SQL1064N DB2STOP processing was successful.
06/08/2012 08:40:34 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
DB20000I The DROP DATABASE command completed successfully.
DB20000I The RESTORE DATABASE command completed successfully.
SQL1265N The archive log file "S0003286.LOG" is not associated with the
current log sequence for database "UPSRVDB" on node "0".
还原时使用的语句：
db2 "restore db upsrvdb from /backup/bak144/dbbak taken at 20120608001002 LOGTARGET /home/db2inst1/DB/target"
db2 "rollforward db upsrvdb to end of backup and complete overflow log path(log path(/home/db2inst1/DB/target)"
在B机器还原只是偶尔会出现上面的错误，有时又能完成还原
A机器所使用日志信息：
First active log file = S0003285.LOG
Logs:
Current Log Number 3286
Pages Written 4738
Method 1 Archive Status Success
Method 1 Next Log to Archive 3286
A机器db2diag.log日志内容如下：
2012-06-07-14.24.10.351799+480 I96806485E369 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0003283.LOG.
2012-06-07-14.24.10.591960+480 I96806855E509 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0003283.LOG to
/backup/archive_log/db2inst1/UPSRVDB/NODE0000/C0000000/ from
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.
2012-06-07-21.56.55.103701+480 I96807365E369 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0003284.LOG.
2012-06-07-21.56.55.349423+480 I96807735E509 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0003284.LOG to
/backup/archive_log/db2inst1/UPSRVDB/NODE0000/C0000000/ from
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.
2012-06-08-00.10.02.582228+480 E96808245E496 LEVEL: Info
PID : 5193 TID : 47271529933120PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : UPSRVDB
APPHDL : 0-1505 APPID: *LOCAL.db2inst1.120607161002
AUTHID : DB2INST1
EDUID : 41347 EDUNAME: db2agent (UPSRVDB) 0
FUNCTION: DB2 UDB, database utilities, sqluxGetDegreeParallelism, probe:507
DATA #1 :
Autonomic backup/restore - using parallelism = 5.
2012-06-08-00.10.03.704933+480 E96808742E523 LEVEL: Info
PID : 5193 TID : 47271529933120PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : UPSRVDB
APPHDL : 0-1505 APPID: *LOCAL.db2inst1.120607161002
AUTHID : DB2INST1
EDUID : 41347 EDUNAME: db2agent (UPSRVDB) 0
FUNCTION: DB2 UDB, database utilities, sqluxGetAvailableHeapPages, probe:618
DATA #1 :
Autonomic BAR - heap consumption.
Targetting (50%) - 55184 of 110368 pages.
2012-06-08-00.10.03.705138+480 E96809266E510 LEVEL: Info
PID : 5193 TID : 47271529933120PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : UPSRVDB
APPHDL : 0-1505 APPID: *LOCAL.db2inst1.120607161002
AUTHID : DB2INST1
EDUID : 41347 EDUNAME: db2agent (UPSRVDB) 0
FUNCTION: DB2 UDB, database utilities, sqlubTuneBuffers, probe:869
DATA #1 :
Autonomic backup - tuning enabled.
Using buffer size = 4097, number = 5.
2012-06-08-00.10.03.979451+480 E96809777E457 LEVEL: Info
PID : 5193 TID : 47271529933120PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : UPSRVDB
APPHDL : 0-1505 APPID: *LOCAL.db2inst1.120607161002
AUTHID : DB2INST1
EDUID : 41347 EDUNAME: db2agent (UPSRVDB) 0
FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:1508
MESSAGE : Starting an online db backup.
2012-06-08-00.10.47.688427+480 I96810235E371 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0003284.LOG.
2012-06-08-00.10.47.960617+480 I96810607E450 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4148
MESSAGE : Completed retrieve for log file S0003284.LOG on chain 0 to
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.
2012-06-08-00.10.47.961117+480 I96811058E369 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
MESSAGE : Started archive for log file S0003285.LOG.
2012-06-08-00.10.51.185184+480 I96811428E509 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
MESSAGE : Completed archive for log file S0003285.LOG to
/backup/archive_log/db2inst1/UPSRVDB/NODE0000/C0000000/ from
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.
2012-06-08-00.10.51.557321+480 I96811938E371 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0003283.LOG.
2012-06-08-00.10.51.931047+480 I96812310E450 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4148
MESSAGE : Completed retrieve for log file S0003283.LOG on chain 0 to
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.
2012-06-08-00.10.51.932112+480 I96812761E371 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4130
MESSAGE : Started retrieve for log file S0003282.LOG.
2012-06-08-00.10.52.168200+480 I96813133E450 LEVEL: Warning
PID : 5193 TID : 47270737209664PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 40279 EDUNAME: db2logmgr (UPSRVDB) 0
FUNCTION: DB2 UDB, data protection services, sqlpgRetrieveLogFile, probe:4148
MESSAGE : Completed retrieve for log file S0003282.LOG on chain 0 to
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/.
2012-06-08-00.10.55.352769+480 E96813584E431 LEVEL: Info
PID : 5193 TID : 47271529933120PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : UPSRVDB
APPHDL : 0-1505 APPID: *LOCAL.db2inst1.120607161002
AUTHID : DB2INST1
EDUID : 41347 EDUNAME: db2agent (UPSRVDB) 0
FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:843
MESSAGE : Backup complete.
2012-06-08-03.20.09.606038+480 E96814016E538 LEVEL: Event
PID : 5193 TID : 47270686878016PROC : db2sysc 0
50同行回答
用以下语句试一下，以下是DB2 V8.2环境下测试通过的在线备份与恢复语句
db2 backup db updsrvdb online to . include logs
如果恢复的日志路径与原日志路径相同，恢复指令为
rm /home/db2inst1/DB/target/*.LOG
db2 restore db upsrvdb from /backup/bak144/dbbak taken at 20120608001002 without prompting
db2 rollforward db upsrvdb to end of logs and stop
如果恢复后日志路径与原数据库日志路径不同，恢复指令为
rm /home/db2inst1/DB/target/*.LOG
db2 "restore db upsrvdb from /backup/bak144/dbbak taken at 20120608001002 LOGTARGET /home/db2inst1/DB/target NEWLOGPATH /home/db2inst1/DB/target"
db2 "rollforward db upsrvdb to end of logs and stop"收起
db2 backup db updsrvdb online to . include logs
如果恢复的日志路径与原日志路径相同，恢复指令为
rm /home/db2inst1/DB/target/*.LOG
db2 restore db upsrvdb from /backup/bak144/dbbak taken at 20120608001002 without prompting
db2 rollforward db upsrvdb to end of logs and stop
如果恢复后日志路径与原数据库日志路径不同，恢复指令为
rm /home/db2inst1/DB/target/*.LOG
db2 "restore db upsrvdb from /backup/bak144/dbbak taken at 20120608001002 LOGTARGET /home/db2inst1/DB/target NEWLOGPATH /home/db2inst1/DB/target"
db2 "rollforward db upsrvdb to end of logs and stop"收起
浏览1513
回复 46# 田强
谢谢田强大哥,上面那段话是摘自这篇文章:http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.ha.doc/doc/c0011559.html?resultof=%22%E5%89%8D%E6%BB%9A%22%20%22logtarget%22%20
谢谢田强大哥,上面那段话是摘自这篇文章:http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.admin.ha.doc/doc/c0011559.html?resultof=%22%E5%89%8D%E6%BB%9A%22%20%22logtarget%22%20
----如果备份数据库时指定了 BACKUP DATABASE 命令的 INCLUDE LOGS 选项，接着执行使用该备份映像的复原操作和前滚操作，那么虽然备份映像包含日志，DB2 在前滚数据库时也仍然会搜索其他事务日志。标准前滚行为会一直搜索其他事务日志，直到找不到更多日志为止。有可能有多个时间戳记相同的日志文件。因此，DB2 在找到第一个与数据库前滚目标时间点匹配的时间戳记时不会立即停止，因为其他日志文件也可能拥有该时间戳记。DB2 将继续查找事务日志，直到找到大于指定时间点的时间戳记为止。
当找不到任何其他日志时，前滚操作将成功地结束。但是，如果搜索其他事务日志文件时出错，就会返回错误 SQL1268N。
就是这一段不太明白,"
rollforward时take一个mask为SQLP,SQLPR的trace",这个倒可以试试
收起浏览1521
Specifying the INCLUDE LOGS option of the BACKUP DATABASE command does not guarantee that DB2® Univ ...weiruan85 发表于 2012-6-21 10:12
onlineback利用了现有的rollforward机制。你需要单独执行rollforward命令对不？所以单就rollforward本身来...Specifying the INCLUDE LOGS option of the BACKUP DATABASE command does not guarantee that DB2® Univ ...
weiruan85 发表于 2012-6-21 10:12
onlineback利用了现有的rollforward机制。你需要单独执行rollforward命令对不？所以单就rollforward本身来讲，它是不受include log的限制的。include log只是告诉online backup包括日志，它会计算该次onlinebackup需要包括哪些日志文件。和rollforward没关系。
所以，如果能够重现还是要开case/pmr啊！收起
浏览1549
回复 38# xu5762173
。因此，DB2 在找到第一个与数据库前滚目标时间点匹配的时间戳记时不会立即停止，因为其他日志文件也可能拥有该时间戳记。DB2 将继续查找事务日志，直到找到大于指定时间点的时间戳记为止。
”直到找到大于指定时间点的时间戳记为止“正确。但时间戳是记在日志记录（日志文件中都是一个一个的log record）中的，不是日志文件的时间戳。其实日志记录这些东西各家厂商包括opensource都差不多的，
当找不到任何其他日志时，前滚操作将成功地结束。但是，如果搜索其他事务日志文件时出错，就会返回错误 SQL1268N。
这里的意思是找到后还不停止呢?
不太明白。。遇到了超过指定PIT的PIT就会停止，如果找不到下一个日志文件了，或者找到了但是该文件里是空的或者是旧的内容也会停止。
你可以rollforward时候take一个mask为SQLP,SQLPR的trace就好理解这个工作流程了
收起
。因此，DB2 在找到第一个与数据库前滚目标时间点匹配的时间戳记时不会立即停止，因为其他日志文件也可能拥有该时间戳记。DB2 将继续查找事务日志，直到找到大于指定时间点的时间戳记为止。
”直到找到大于指定时间点的时间戳记为止“正确。但时间戳是记在日志记录（日志文件中都是一个一个的log record）中的，不是日志文件的时间戳。其实日志记录这些东西各家厂商包括opensource都差不多的，
当找不到任何其他日志时，前滚操作将成功地结束。但是，如果搜索其他事务日志文件时出错，就会返回错误 SQL1268N。
这里的意思是找到后还不停止呢?
不太明白。。遇到了超过指定PIT的PIT就会停止，如果找不到下一个日志文件了，或者找到了但是该文件里是空的或者是旧的内容也会停止。
你可以rollforward时候take一个mask为SQLP,SQLPR的trace就好理解这个工作流程了
收起
浏览1533
另外。 当前滚不成功，报出
SQL1265N The archive log file "S0003325.LOG" is not associated with the ...
Y1YI 发表于 2012-6-21 09:03
这个和notrieve达到的workaround效果类似。收起
浏览1515