how to rollforward without userexit - SQL1268N

[darnold]

I have restored a clients database using a redirected restore. However,
it is in a roll forward pending state. When I try to to a roll forward
to end of the logs, I get
SQL1268N Roll-forward recovery stopped due to error "1" while
retrieving log....

I have all of the logs, including the one mentioned in the SQL1268N
message. And they are in the log directory
I have tried changing userexit to no, and logretain to recovery.

Is there a way to roll forward without the customer's user exit
program? or pehaps there is something else I have missed here?

Regards
Dave Arnold

[Phil Sherman]

Are you restoring the database on the same instance from which the
backups were made on or you trying to build a duplicate database
somewhere else?

Philip Sherman
da*****@carreke r.com wrote:

I have restored a clients database using a redirected restore. However,
it is in a roll forward pending state. When I try to to a roll forward
to end of the logs, I get
SQL1268N Roll-forward recovery stopped due to error "1" while
retrieving log....

I have all of the logs, including the one mentioned in the SQL1268N
message. And they are in the log directory
I have tried changing userexit to no, and logretain to recovery.

Is there a way to roll forward without the customer's user exit
program? or pehaps there is something else I have missed here?

Regards
Dave Arnold

[DaveA]

Philip,
I am building a duplicate database. This is a customer data base that
we need to install on our site for a project. We have the backup and
logs, but do not have their user exit pgm.

One other thought I had over the weekend was to try to use the sample
Windows db2uext2.cdisk. But I was hoping for an easier solution

Dave

[Knut Stolze]

DaveA wrote:

Philip,
I am building a duplicate database. This is a customer data base that
we need to install on our site for a project. We have the backup and
logs, but do not have their user exit pgm.

One other thought I had over the weekend was to try to use the sample
Windows db2uext2.cdisk. But I was hoping for an easier solution

Is there anything in the log files that you really need? If not, you could
do the restore with the WITHOUT ROLLING FORWARD option. Then the backup
image is applied only.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

[Keith]

For a restore from an online backup image, one would still need to
supply all/any logs till the end of backup operation. DB2 will still
play thru these minimum logs even if there aren't any transactions.
WITHOUT ROLLING FORWARD will not help in this case.

Can you take an offline backup and restore?

BTW, Per V7.2 documentation (Administration Guide: Implementation) ,
error 1 treated as error 32 - "The user exit was terminated by the
user"

Keith Ponnapalli
adv_dba at yahoo dot com
IBM Certified Advanced Database Administrator - DB2 UDB V8.1 for Linux,
UNIX, and Windows
INFORMIX Certified Database Administrator

Knut Stolze wrote:

DaveA wrote:

Philip,
I am building a duplicate database. This is a customer data base that
we need to install on our site for a project. We have the backup and
logs, but do not have their user exit pgm.

One other thought I had over the weekend was to try to use the sample
Windows db2uext2.cdisk. But I was hoping for an easier solution

Is there anything in the log files that you really need? If not, you could
do the restore with the WITHOUT ROLLING FORWARD option. Then the backup
image is applied only.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

[DaveA]

Knut,
Thanks for the suggestion. Ultimatly we need all the data, but I tried
your suggestion with the hope that at least that would give us some
data to get started, but I got error SQL2537N Roll-forward is required
following the Restore.

Frankly, I am somewhat surprised I have seen no postings on this
problem. What I am trying to do seems like a normal requirement
Certainly we do it all the time with other customers. I suspect this is
the first time though that we have encountered the use of the user
exit.

[Knut Stolze]

Keith wrote:

For a restore from an online backup image, one would still need to
supply all/any logs till the end of backup operation. DB2 will still
play thru these minimum logs even if there aren't any transactions.
WITHOUT ROLLING FORWARD will not help in this case.

This is true. At some point (V8.2?) the logs written during the backup
operation are already included in the backup image. But that's all
guessing because we don't know the details.

Another idea might be to create the database, restore it from the backup
image, then copy the logs to the respective directory and then do the
rollforward. W/o the user exit being activated, DB2 might (I don't know
for sure) search for the log files in the logpath. When rollforward finds
it there, you're happy.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

[Phil Sherman]

Since you needed a redirected restore, I assume that the disk
architecture/directory structure doesn't match the production system.

Did you make sure that the database log location, after restore, points
to the correct drive/path where you copied the logs? If you have to have
the user exit, you could write one that indicates the log is available
in the appropriate directory without actually doing anything.

Phil Sherman

DaveA wrote:

Philip,
I am building a duplicate database. This is a customer data base that
we need to install on our site for a project. We have the backup and
logs, but do not have their user exit pgm.

One other thought I had over the weekend was to try to use the sample
Windows db2uext2.cdisk. But I was hoping for an easier solution

Dave

[Tim]

Hi Dave

What I would suggest is once you have the database restored but not yet
rolled forward, do a db2 get db cfg for ae12sym and look for the line
with Path to log files in it. Then put all the logs you need for
rolling forward in this directory, make sure aren't compressed or
anything like that and that they all have a name of the format
Snnnnnnn.LOG. At this point a simple db2 rollforward database stop
should work just fine assuming you only want to take the database out
of rollforward pending.

If you do want to rollforward pass the necessary arguements to db2
rollforward database. All DB2 wants is having the logs in a place
where it can get to them. A user exit is pretty much useless in a
redirected restore into another database as far as I know (feel free to
correct me if I'm wrong).

regards
tim

[DaveA]

Tim,
Thankyou! The stop option was what finally resolved this for me.

Dave.