roll-forward pending state

[xxge...@yahoo.com]

Hi all,

I'm using DB2 6.1 on NT platform and I'm trying out online backup. I have no
problem in backup but I cannot restore it properly. I understand that it
needs retreiving information from log after restoring, but after I've
finished restoring (which is successful, according to the journal), I cannot
connect to the database.

The error message is:

[IBM][CLI Driver] SQL1117N A connection to or activation of database "XXX"
cannot be made because of ROLL-FORWARD PENDING. SQLSTATE=57019

I tried to execute the "roll-forward" option from control center, but that
doesn't help. So how can I 'escape' from this pending state?

Thanks a lot

George

Sent via Deja.com http://www.deja.com/
Before you buy.

[Paul]

If you actually don't want to restore/roll forward but only want to restore, do
another restore and add 'without rolling forward' as part of the command. i.e.

db2 restore db xyz from d:\db2backup using x buffers replace existing
without prompting without rolling forward

Please review the command and it's consideration of log files in the
Administration Guide and the Command Reference.

[Dale McInnis]

Paul
This is not valid for an online backup. The minimum rollforward Point In Time for
an online backup is the time at which the backup completed.. In order to restore
an online backup to another machine you need to copy the log files from your source
machine to you target after the restore has completed. As of DB2 V7 we will
truncate the active log after the online backup has completed.

Dale McInnis

[Paul]

Perhaps I misread the issue. I thought the point is that when George is performing a
restore the database is being left in a roll-forward pending state. Performing a
restore with the 'without rolling forward' should produce the desired result of restore
recovery and leave the database in a consistent state. I didn't see anywhere where
restoring an online backup to another machine was discussed.

[xxge...@yahoo.com]

Hi all,

I think the problem may arise from that I'm restoring the image to a new
database.

As I'm trying to procedure on the same machine, I simulate the worst
situation: drop the existing database, creating a new one with same name and
alias, and then restore from the backup image. (for online backup image,
roll-forward must be performed). By the end, the database remains in
roll-forward pending state. I guess it is because DB2 cannot find the log
for this new database, though identical name?

In another case, if I don't drop the database and choose restore, Control
Center can locate all the images for me and there is not any problem after
finished.

George

In article <396BE69B...@swbell.net>,

[xxge...@yahoo.com]