By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,851 Members | 1,729 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,851 IT Pros & Developers. It's quick & easy.

ROLLFORWARD QUESTION

P: n/a
DB2 V8.1.5 on Windows.
When I execute ROLLFORWARD after a Restore.
C:\db2 ROLLFORWARD db sample to END OF LOGS overflow log path(C:\LOGS\)
Rollforward Status

Input database alias = sample
Number of nodes have returned status = 1

Node number = 0
Rollforward status = DB working
Next log file to be read = S0007342.LOG
Log files processed = S0007068.LOG - S0007340.LOG
Last committed transaction = 2004-08-22-03.32.09.000000

How come the processed Log and Next log to be read is not continuous?
I do see the last log file is S0007341.LOG, from the result of
Rollforward, it was not processed at all.
Any explanation?
Thanks
Anwei

Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
AnWei,
If you could continue run rollforward processing then check the rollforward
status, or you decide to terminate "rollforward pending" by run "rollforward
complete (or stop)", you could find out if rollforward process deal with
S0007341.LOG or not.

<sh*******@gmail.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
DB2 V8.1.5 on Windows.
When I execute ROLLFORWARD after a Restore.
C:\db2 ROLLFORWARD db sample to END OF LOGS overflow log path(C:\LOGS\)
Rollforward Status

Input database alias = sample
Number of nodes have returned status = 1

Node number = 0
Rollforward status = DB working
Next log file to be read = S0007342.LOG
Log files processed = S0007068.LOG - S0007340.LOG
Last committed transaction = 2004-08-22-03.32.09.000000

How come the processed Log and Next log to be read is not continuous?
I do see the last log file is S0007341.LOG, from the result of
Rollforward, it was not processed at all.
Any explanation?
Thanks
Anwei

Nov 12 '05 #2

P: n/a
When issue Rollforward stop, get this error.
SQL4970N Roll-forward recovery on database "sample" cannot reach the
specified stop point (end-of-log or point-in-time) because of missing
log
file(s) on node(s) "0".

Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.