cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

rollforward issue

Former Member
0 Likes
532

Hi All,

We are on client refresh process so far we completed restore process till now but when i try to do the rollforward i got below error...

IMU-IQB:db2gqb 13> 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 "S0110861.LOG".

Appreciated your help on this..

Panu

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Likes

Kumar -

First of all I would find where you have all the logfiles located that you will be using for the rollforward. They may be in a different path that what you are expecting. Once you know the path, then use the overflow log path option to the rollforward and complete command.

rollforward db gqb to end of logs overflow log path ( /path/to/your/log/files )

db2 rollforward db gqb complete overflow log path ( /path/to/your/log/files )

Andrew

paul_power
Product and Topic Expert
Product and Topic Expert
0 Likes

Dear Panu,

The rollforward seems to fail as it cannot find the required log file

S0110861.LOG

does this log file exist and can it be made available to the db for rollforward ?

If it has been lost or is corrupt, then you will only be able to rollforward to the closest existing, usable log file

e.g. S0110860.LOG and then stop the rollforward to bring the db online.

Regards,

Paul

Former Member
0 Likes

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 = S0110861.LOG

Log files processed = -

Last committed transaction = 2011-04-29-08.05.05.000000 UTC

========================

db2diag.log file as below

2011-05-03-07.20.22.858439+060 I71147501A421 LEVEL: Error

PID : 434404 TID : 1 PROC : db2redom (GQB) 0

INSTANCE: db2gqb NODE : 000 DB : GQB

APPHDL : 0-27 APPID: *LOCAL.db2gqb.110503061833

AUTHID : DB2GQB

FUNCTION: DB2 UDB, data protection services, sqlpgPostLoggrWithoutLatching, probe:930

MESSAGE : db2logger: rc=-2146434885 sem rc=0 type=27

2011-05-03-07.20.22.858627+060 I71147923A145 LEVEL: Error

PID:434404 TID:1 NODE:000 Title: SQLP_DBCB

Dump File:/db2/GQB/db2dump/4344041.000

2011-05-03-07.20.22.859096+060 I71148069A449 LEVEL: Error

PID : 434404 TID : 1 PROC : db2redom (GQB) 0

INSTANCE: db2gqb NODE : 000 DB : GQB

APPHDL : 0-27 APPID: *LOCAL.db2gqb.110503061833

AUTHID : DB2GQB

FUNCTION: DB2 UDB, recovery manager, sqlpPRecReadLog, probe:3980

RETCODE : ZRC=0x801000BB=-2146434885=SQLPR_MISSING_LOGFILES

"rollforward missing log files"

2011-05-03-07.20.23.063727+060 I71148519A452 LEVEL: Error

PID : 471286 TID : 1 PROC : db2agent (GQB) 0

INSTANCE: db2gqb NODE : 000 DB : GQB

APPHDL : 0-27 APPID: *LOCAL.db2gqb.110503061833

AUTHID : DB2GQB

FUNCTION: DB2 UDB, recovery manager, sqlprDoForwardPhase, probe:330

RETCODE : ZRC=0x801000BB=-2146434885=SQLPR_MISSING_LOGFILES

"rollforward missing log files"

2011-05-03-07.20.23.063962+060 I71148972A453 LEVEL: Error

PID : 471286 TID : 1 PROC : db2agent (GQB) 0

INSTANCE: db2gqb NODE : 000 DB : GQB

APPHDL : 0-27 APPID: *LOCAL.db2gqb.110503061833

AUTHID : DB2GQB

FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecovery, probe:1230

RETCODE : ZRC=0x801000BB=-2146434885=SQLPR_MISSING_LOGFILES

"rollforward missing log files"

2011-05-03-07.20.23.064710+060 E71149426A421 LEVEL: Warning

PID : 471286 TID : 1 PROC : db2agent (GQB) 0

INSTANCE: db2gqb NODE : 000 DB : GQB

APPHDL : 0-27 APPID: *LOCAL.db2gqb.110503061833

AUTHID : DB2GQB

FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:8180

MESSAGE : ADM1611W The rollforward recovery phase has been completed.

2011-05-03-08.01.56.005852+060 I71149848A427 LEVEL: Severe

PID : 471286 TID : 1 PROC : db2agent (GQB) 0

INSTANCE: db2gqb NODE : 000

APPHDL : 0-28 APPID: *LOCAL.db2gqb.110503070155

AUTHID : DB2GQB

FUNCTION: DB2 UDB, base sys utilities, sqleFirstConnect, probe:100

DATA #1 : Hexdump, 4 bytes

0x000000011135B26C : FFFF FBA3 ....

2011-05-03-08.01.56.034825+060 I71150276A300 LEVEL: Warning

PID : 430316 TID : 1 PROC : db2bp

INSTANCE: db2gqb NODE : 000

FUNCTION: DB2 UDB, Connection Manager, sqleUCappImpConnect, probe:150

RETCODE : ZRC=0x8037006D=-2143879059=SQLJR_CABLT "CA BUILT"

2011-05-03-08.02.22.540174+060 I71150577A427 LEVEL: Severe

PID : 471286 TID : 1 PROC : db2agent (GQB) 0

INSTANCE: db2gqb NODE : 000

APPHDL : 0-29 APPID: *LOCAL.db2gqb.110503070222

AUTHID : DB2GQB

FUNCTION: DB2 UDB, base sys utilities, sqleFirstConnect, probe:100

DATA #1 : Hexdump, 4 bytes

0x000000011135B26C : FFFF FBA3 ....

2011-05-03-08.02.26.568616+060 I71151005A368 LEVEL: Warning

PID : 471286 TID : 1 PROC : db2agent (GQB) 0

INSTANCE: db2gqb NODE : 000

APPHDL : 0-30 APPID: *LOCAL.db2gqb.110503070223

AUTHID : DB2GQB

FUNCTION: DB2 UDB, relation data serv, sqlrr_db_init, probe:100

MESSAGE : DB2_IMPLICIT_UNICODE enabled

GMU-BIQB:db2gqb 39>