Question Re: rollforward issue in Technology Q&A

rollforward issue

Former Member — Sun, 10 Jul 2011 06:11:36 GMT

We have successfully restore from TSM but when we perform rollback got error as below.

ON /db2/GQB/sapdata6 ,/db2/GQB/sapdata5 ,/db2/GQB/sapdata4 ,/db2/GQB/sapdata3 ,/db2/GQB/sapdata2 ,/db2/GQB/sapdata1 DBPATH ON /db2/GQB INTO GQB LOGTARGET /db2/GQB/log_dir/NODE0000/ WITH 2 BUFFERS BUFFER 1024

SQL2528W Warning! Restoring to an existing database that is the same as the

backup image database, but the alias name "GQB" of the existing database does

not match the alias "GPB" of backup image, and the database name "GQB" of the

existing database does not match the database name "GPB" of the backup image.

The target database will be overwritten by the backup version.

Do you want to continue ? (y/n) y

SQL2580W Warning! Restoring logs to a path which contains existing log files.

Attempting to overwrite an existing log file during restore will cause the

restore operation to fail.

Do you want to continue ? (y/n) y

DB20000I The RESTORE DATABASE command completed successfully.

***********************************************************

THE RESTORE PROCEDURE HAS NOW FINISHED SUCCESSFULLY **

***********************************************************

GMU-BIQB:db2gqb 56> db2 rollforward db GQB to end of logs

SQL4970N Roll-forward recovery on database "GQB" cannot reach the specified

stop point (end-of-log or point-in-time) because of missing or corrupted log

file(s) on database partition(s) "0". Roll-forward recovery processing has

halted on log file "S0130978.LOG".

GMU-BIQB:db2gqb 57> db2 rollforward db GQB complete

SQL1276N Database "GQB" cannot be brought out of rollforward pending state

until roll-forward has passed a point in time greater than or equal to

"2011-07-08-08.18.22.000000 UTC", because node "0" contains information later

than the specified time.

Appreciated your help on this.

Regards,

Kumar

Re: rollforward issue

Former Member — Sun, 10 Jul 2011 08:52:27 GMT

db2 rollforward db GQB query status

Rollforward Status

Input database alias = GQB

Number of nodes have returned status = 1

Node number = 0

Rollforward status = DB working

Next log file to be read = S0130978.LOG

Log files processed = -

Last committed transaction = 2011-07-08-08.18.22.000000 UTC

GMU-BIQB:db2gqb 75> db2 "rollforward database GQB to end of logs OVERFLOW LOG PATH (/db2/GQB/log_dir)"

SQL4970N Roll-forward recovery on database "GQB" cannot reach the specified

stop point (end-of-log or point-in-time) because of missing or corrupted log

file(s) on database partition(s) "0". Roll-forward recovery processing has

halted on log file "S0130978.LOG".

Re: rollforward issue

Former Member — Sun, 10 Jul 2011 08:55:44 GMT

I am also facing the same issue ....

Can somebody please help ?

thanks in advance,

RajaG

Re: rollforward issue

marc_saulnier — Sun, 10 Jul 2011 21:43:59 GMT

Hi try this command :

db2 "rollforward db GQB stop OVERFLOW LOG PATH (/db2/GQB/log_dir)"

let me know

regards

Re: rollforward issue

Former Member — Mon, 11 Jul 2011 00:39:56 GMT

Hi Marc,

I tried the same and got the below error :

SQL1276N Database "M03" cannot be brought out of rollforward pending state

until roll-forward has passed a point in time greater than or equal to

"2011-06-18-04.50.00.000000 UTC", because node "0" contains information later

than the specified time.

Can you please advise ?

thanks,

Raj

Re: rollforward issue

marc_saulnier — Mon, 11 Jul 2011 01:51:49 GMT

Hi it's look like db2 did not find the log S0130978.LOG under /db2/GQB/log_dir. If the log file is not under this directory, you need to restore the log file.

This is an exemple using brrestore with TSM :

Step 1 : db2 rollforward db GQB query status and note "Next log file to be read"

Step 2 : cd /db2/GQB/log_dir *To dump the log under this directory

Step 3 : brrestore -q "NODE" -out -sid GQB *To query the log file available

Step 4 : brrestore -ex "S0130978.LOG*" -d adsm -sid GQB

Step 5 : Rename the log file with the appropriate name ie: S0130978.LOG and make sure the file is under /db2/GQB/log_dir

Step 6 : db2 "rollforward db GQB stop OVERFLOW LOG PATH (/db2/GQB/log_dir)"

CHeck that !

regards

Re: rollforward issue

Former Member — Mon, 11 Jul 2011 02:32:56 GMT

Hi Marc,

You are correct, the appropriate logs are not found in /db2/M03/log_dir

But, It seems we dont have this "brrestore" command :

db2m03> man -k brrestore

brrestore: Cannot find matching entry.

Is there any other way to retrieve the logs from TSM ?

Thanks,

Raj

Re: rollforward issue

Former Member — Mon, 11 Jul 2011 03:04:22 GMT

Hi Marc,

Please find output as below

db2 "rollforward db GQB stop OVERFLOW LOG PATH (/db2/GQB/log_dir)"

SQL1276N Database "GQB" cannot be brought out of rollforward pending state

until roll-forward has passed a point in time greater than or equal to

"2011-07-10-08.06.59.000000 UTC", because node "0" contains information later

than the specified time.

db2 rollforward db GQB to 2011-07-10-08.06.59.000000

SQL1274N The database "GQB" requires roll-forward recovery and the

point-in-time must be to the end of logs.

db2 rollforward db GQB to end of logs

SQL4970N Roll-forward recovery on database "GQB" cannot reach the specified

stop point (end-of-log or point-in-time) because of missing or corrupted log

file(s) on database partition(s) "0". Roll-forward recovery processing has

halted on log file "S0131143.LOG".

db2 rollforward db GQB query status

Rollforward Status

Input database alias = GQB

Number of nodes have returned status = 1

Node number = 0

Rollforward status = DB working

Next log file to be read = S0131143.LOG

Log files processed = -

Last committed transaction = 2011-07-10-08.06.59.000000 UTC

But this file S0131143.LOG exist in /db2/GQB/log_dir/NODE0000.

Kumar

Re: rollforward issue

marc_saulnier — Mon, 11 Jul 2011 12:05:40 GMT

Hi Kumar if the log exist point the overflow log path on this directory

db2 "rollforward db GQB stop OVERFLOW LOG PATH (/db2/GQB/log_dir/NODE0000

regards

Re: rollforward issue

marc_saulnier — Mon, 11 Jul 2011 12:28:43 GMT

Hi you need to use db2adutl in this case :

Step 1 : db2 rollforward db GQB query status and note "Next log file to be read"

Step 2 : cd /db2/GQB/log_dir *To dump the log under this directory

Step 3 : db2adutl query logs

Step 4 : db2adutl extract logs between S0084324.LOG AND S0084325.LOG * The LOG sequence you want to retrieve

Step 5 : Rename the log file with the appropriate name ie: S0130978.LOG and make sure the file is under /db2/GQB/log_dir

Step 6 : db2 "rollforward db GQB stop OVERFLOW LOG PATH (/db2/GQB/log_dir)"

regards

Re: rollforward issue

Former Member — Wed, 13 Jul 2011 02:22:07 GMT

thanks a lot Marc, that worked.

but I have another issue now

db2m03> db2 rollforward db M03 to end of logs

SQL1268N Roll-forward recovery stopped due to error "SQL2033" while

retrieving log file "S0059505.LOG" for database "M03" on node "0".

Please help me how to bring the database to a consistent state ASAP.

Thanks in advance,

Raj

Re: rollforward issue

marc_saulnier — Wed, 13 Jul 2011 03:13:31 GMT

Hi. did you try the command as specify in step 6 ?

Regards

Re: rollforward issue

Former Member — Wed, 13 Jul 2011 03:52:19 GMT

Dear Marc,

thanks again for the help

I just extracted the log(s) it specified as missing...and then gave a rollforward to end of logs

i believe its success now.

db2m03> db2 rollforward db M03 query status

Rollforward Status

Input database alias = M03

Number of nodes have returned status = 1

Node number = 0

Rollforward status = not pending

Next log file to be read =

Log files processed = S0059488.LOG - S0059506.LOG

Last committed transaction = 2011-06-18-07.02.03.000000 UTC

Please correct if anythign is wrong...

Re: rollforward issue

marc_saulnier — Wed, 13 Jul 2011 11:57:14 GMT

Nice, everything look good now.

Congratulation

Re: rollforward issue

Former Member — Wed, 27 Nov 2013 20:09:20 GMT

hii

i am also facing same problem

can u guide me how to resolve it

please my production server is down