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 IC70431 Status: Closed

ABEND ON HADR PRIMARY DUE TO BADLOG ERROR IN SQLPGWRITETODISK

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A HADR primary database can fail with the following message : 
 
EDUID   : 23                   EDUNAME: db2loggw (SAMPLE) 
FUNCTION: DB2 UDB, data protection services, sqlpgWriteToDisk, 
probe:909 
MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File 
cannot be used" 
          DIA8414C Logging can not continue due to an error. 
DATA #1 : <preformatted> 
TailPage 0 does not match pagelsn 0015AD388052 and firstlsn 
0015AE388000 
 
This is typically seen after a non forced takeover and when 
mirrored logging is enabled. ( mirrorlogpath set in the db cfg 
). 
 
Another eyecatcher is the following error that may happen some 
time prior to this during the takeover : 
 
2010-06-17-15.55.59.401076+120 I125515E447         LEVEL: Severe 
PID     : 21100                TID  : 183236553056 PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 39                   EDUNAME: db2hadrs (SAMPLE) 
 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrAddLogFiles, probe:10150 
RETCODE : ZRC=0x071000E3=118489315=SQLP_RETRY_GADF 
"sqlpgCallGIFL: block on log disk.  sqlpgReuseCAL: log file 
deleted"
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* HADR users                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Potential outage on the hadr primary with a BADLOG error.    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade DB2 server to V9.7 Fixpak 4                          * 
****************************************************************
Local Fix:
The primary database recovers from this after a database 
restart.
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This problem has been fixed in V9.7 Fixpak 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.08.2010
24.05.2011
24.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList