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

Last commited transaction less then backup image timestamp after restore with rollforward?

P: n/a
Hi ,
I run restore with rollforward
In job in output, last commited transaction time less then backup image
time
Is it normal ?

RESTORE DATABASE PRICE_V8 FROM "E:\BACKUP" TAKEN AT 20050610095841 TO
"D:" INTO PR_READ NEWLOGPATH "D:\DB2_FILES\PR_READ\LOG" WITH 2 BUFFERS
BUFFER 1024 REDIRECT PARALLELISM 1 WITHOUT PROMPTING
.....
RESTORE DATABASE PRICE_V8 CONTINUE
DB20000I The RESTORE DATABASE command completed successfully.
.....
ROLLFORWARD DATABASE PR_READ TO 2005-06-10-10.59.50.000000 USING LOCAL
TIME AND STOP OVERFLOW LOG PATH
(\\DB2_LOGSSERVER\\DB_ARCHIVE_FILES\PRICE_V8\\)

Rollforward Status

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

Node number = 0
Rollforward status = not pending
Next log file to be read =
Log files processed = -
Last committed transaction = 2005-06-09-14.28.34.000000

DB20000I The ROLLFORWARD command completed successfully.

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


P: n/a
It's unlikely that the last committed transaction time is the same as
the "rollforward to" time you picked. The status report indicates that
there was no activity after the last committed transaction or that any
active work completed after the time you picked and should have been
rolled back as part of the rollforward process. It looks like this
database wasn't very busy.
Phil Sherman

t2***@hotmail.com wrote:
Hi ,
I run restore with rollforward
In job in output, last commited transaction time less then backup image
time
Is it normal ?

RESTORE DATABASE PRICE_V8 FROM "E:\BACKUP" TAKEN AT 20050610095841 TO
"D:" INTO PR_READ NEWLOGPATH "D:\DB2_FILES\PR_READ\LOG" WITH 2 BUFFERS
BUFFER 1024 REDIRECT PARALLELISM 1 WITHOUT PROMPTING
....
RESTORE DATABASE PRICE_V8 CONTINUE
DB20000I The RESTORE DATABASE command completed successfully.
....
ROLLFORWARD DATABASE PR_READ TO 2005-06-10-10.59.50.000000 USING LOCAL
TIME AND STOP OVERFLOW LOG PATH
(\\DB2_LOGSSERVER\\DB_ARCHIVE_FILES\PRICE_V8\\)

Rollforward Status

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

Node number = 0
Rollforward status = not pending
Next log file to be read =
Log files processed = -
Last committed transaction = 2005-06-09-14.28.34.000000

DB20000I The ROLLFORWARD command completed successfully.

Nov 12 '05 #2

P: n/a
Hi Phil,
I use db2uext2 for archiving
db backup created at 20050610095841 ,then I run insert till I see 10
new log files in archive directory
D:\DB2_LOGSSERVER\DB_ARCHIVE_FILES\PRICE_V8

them I run restore and rollforward to time just 1 minute less then my
last
archived log file and expect to see new transaction...

Thanks
Alex
Phil Sherman wrote:
It's unlikely that the last committed transaction time is the same as
the "rollforward to" time you picked. The status report indicates that
there was no activity after the last committed transaction or that any
active work completed after the time you picked and should have been
rolled back as part of the rollforward process. It looks like this
database wasn't very busy.
Phil Sherman

t2***@hotmail.com wrote:
Hi ,
I run restore with rollforward
In job in output, last commited transaction time less then backup image
time
Is it normal ?

RESTORE DATABASE PRICE_V8 FROM "E:\BACKUP" TAKEN AT 20050610095841 TO
"D:" INTO PR_READ NEWLOGPATH "D:\DB2_FILES\PR_READ\LOG" WITH 2 BUFFERS
BUFFER 1024 REDIRECT PARALLELISM 1 WITHOUT PROMPTING
....
RESTORE DATABASE PRICE_V8 CONTINUE
DB20000I The RESTORE DATABASE command completed successfully.
....
ROLLFORWARD DATABASE PR_READ TO 2005-06-10-10.59.50.000000 USING LOCAL
TIME AND STOP OVERFLOW LOG PATH
(\\DB2_LOGSSERVER\\DB_ARCHIVE_FILES\PRICE_V8\\)

Rollforward Status

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

Node number = 0
Rollforward status = not pending
Next log file to be read =
Log files processed = -
Last committed transaction = 2005-06-09-14.28.34.000000

DB20000I The ROLLFORWARD command completed successfully.


Nov 12 '05 #3

P: n/a
PMFJI, this may be a stupid comment on my part but what time zone are you
in.
You roll forward to LOCAL TIME but if I remember right, the output of the
message is always in UCT time
Regards, Pierre.

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
<t2***@hotmail.com> a écrit dans le message de news:
11*********************@f14g2000cwb.googlegroups.c om...
Hi ,
I run restore with rollforward
In job in output, last commited transaction time less then backup image
time
Is it normal ?

RESTORE DATABASE PRICE_V8 FROM "E:\BACKUP" TAKEN AT 20050610095841 TO
"D:" INTO PR_READ NEWLOGPATH "D:\DB2_FILES\PR_READ\LOG" WITH 2 BUFFERS
BUFFER 1024 REDIRECT PARALLELISM 1 WITHOUT PROMPTING
....
RESTORE DATABASE PRICE_V8 CONTINUE
DB20000I The RESTORE DATABASE command completed successfully.
....
ROLLFORWARD DATABASE PR_READ TO 2005-06-10-10.59.50.000000 USING LOCAL
TIME AND STOP OVERFLOW LOG PATH
(\\DB2_LOGSSERVER\\DB_ARCHIVE_FILES\PRICE_V8\\)

Rollforward Status

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

Node number = 0
Rollforward status = not pending
Next log file to be read =
Log files processed = -
Last committed transaction = 2005-06-09-14.28.34.000000

DB20000I The ROLLFORWARD command completed successfully.


Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.