|
Problem IT19430
|
Status: Closed |
ROLLFOWARD FAILS DUE TO PRIMARY OR MIRROR LOG PATH MARKED BAD AFTER RESTORE |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
In a situation in which the backup was taken while the Primary
or Mirror log path was marked bad on the source. When the
rollforward retrieves the logs to the path and then attempts to
use them, the rollforward will fail at the end.
You will see repeating messages like the following during the
retrieve and rollforward phase:
2016-02-11-22.36.33.018583+000 I26866590E559 LEVEL:
Severe
PID : 17463 TID : 46926980441856 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
HOSTNAME: myhost.com
EDUID : 344 EDUNAME: db2lfr.0 (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services,
sqlplfrGetFileHandleToReadFrom, probe:5260
DATA #1 : <preformatted>
LFR Scan Num = 3
LFR Scan Caller's EDUID = 395
Both log paths seem to be bad, try path2. extentNum = 13402
and then at the end when it goes to complete the rollforward it
will fail with the following message:
2016-02-11-22.36.46.713348+000 E26873005E608 LEVEL:
Error
PID : 17463 TID : 46925562767104 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
HOSTNAME: myhost.com
EDUID : 342 EDUNAME: db2loggr (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services, sqlpgarl,
probe:2160
MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic
Error"
DIA8526C A fatal error occurred in data protection
services.
DATA #1 : <preformatted>
Log 13402 on log stream 0 is bad on both log paths. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 9 or higher *
**************************************************************** |
| Local Fix: |
Manually copy the log files to the "other" path (the one not
marked bad) and the rollforward should succeed. |
| Solution |
First fixed in Db2 10.5 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.02.2017
29.09.2017
29.09.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
