home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT09285 Status: Closed

ROLLFORWARD MAY FAIL WITH SQL1042C WHEN MIRRORLOGPATH IS USED

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When the MIRRORLOGPATH is used and MFH in the backup image 
indicates that the log file is not usable on the active path for 
some reason(actually the logpath is usable at the rollforward 
timing), "rollforward db complete" command may fail with 
SQL1042C and following error message is logged in db2diag.log: 
 
2015-01-01-00.00.01.123456+540 E1386726A563         LEVEL: Error 
PID     : 12345678             TID : 12345          PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
SAMPLE 
HOSTNAME: myhost 
EDUID   : 12345                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 1234 on log stream 2 is bad on both log paths. 
 
With the fix for this APAR, rollforward handles this condition. 
We know that we used the log during forward phase, so we know 
the file is good, we should update the MFH during forward phase 
so that when we try to use it in backward phase, it will be 
marked good.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 7.                      * 
****************************************************************
Local Fix:


Solution


First fixed in DB2 Version 10.5 Fix Pack 7.


Workaround


not known / see Local fix


Timestamps


Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

04.06.2015
29.01.2016
29.01.2016


Problem solved at the following versions (IBM BugInfos)




Problem solved according to the fixlist(s) of the following version(s)


10.5.0.7

FixList