DB2 UDB restore problem

[Larry K. Smith]

We are running DB2 UDB v5 (fix livel 9045) on an NT/4.0 system.
A database became corrupted by a LOAD process that failed, and we have
been unable to restore the database to a usable state. After a restore
completes, the database is put into rollforward-pending state; the
log files needed for the roll forward, however, seem to be missing.
We would be satisfied to restore the database from the last backup
and leave it at that, but all our attempts to tell the restore process
that we don't want to do a roll forward have been unsuccessful. The
database is always put into the rollforward-pending state and we have
been unable to find a way to clear this condition.

How can we restore the database to a point in time and leave it in
a normal state without doing a rollforward?

Here's a sequence of db2 commands and responses that might help to
clarify the problem (this is after a restore, and the database is in a
rollforward-pending state):

---------------------------------------------

db2 => rollforward db aus_nt to end of logs and stop
SQL4970N Roll-forward recovery on database "AUS_NT" cannot reach the
specified stop point (end-of-log or point-in-time) because of missing
log file(s) on node(s) "0".
db2 =>

----------------------------

db2 =>
db2 => rollforward db aus_nt query status

Rollforward Status

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

Node number = 0
Rollforward status = DB working
Next log file to be read = S0000393.LOG
Log files processed = -
Last committed transaction = 1998-12-03-11.45.23.000000

-------------------------------------

db2 => rollforward db aus_nt to 1998-12-03-11.45.23.000000 and stop
SQL1266N Database "AUS_NT" has been rolled forward to
"2106-02-06-06.28.15.000000", which is past the specified
point-in-time.
db2 =>

-------------------

db2 => connect to aus_nt
SQL1117N A connection to or activation of database "AUS_NT" cannot
be made because of ROLL-FORWARD PENDING. SQLSTATE=57019
db2 =>

------------------

db2 => rollforward db aus_nt complete
SQL1276N Database "AUS_NT" cannot be brought out of rollforward
pending state until roll-forward has passed a point in time greater
than or equal to "1998-12-03-12.03.40.000000", because node "0"
contains information later than the specified time.
db2 =>

----------------------------------------

Thanks in advance for any input.

Larry Smith
smi...@mail.auburn.edu

[Rodney Merritt]

I have performed a restore on our test database without rolling forward
even though forward recovery is turned on. You might try the same thing and
see if it works for you. I used the GUI screens to initiate the restore and
on the Roll-Forward page, I made sure both the 'roll forward' and 'leave in
roll forward pending state' radio buttons were NOT checked. In that case it
restored the database 'to copy' to use the mainframe term, and it was ready
to use.

Rod Merritt
Harte-Hanks Response Management