home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC80349 Status: Geschlossen

DB2 HADR STANDBY MARKED BAD DUE TO "LOG PAGE CHECKSUM MISMATCH"

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
A HADR standby using superasync synchronous mode could hit log 
page checksum mismatch issue bringing down the standby database. 
Please look into the DB2 diaglog.log file for the relevant 
messages similar to the below ones. 
 
2011-11-26-04.02.07.346200-300 I398177E457         LEVEL: Error 
PID     : 1593                 TID  : 140118371329792PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000          DB   : HDRLNX 
APPHDL  : 0-8                  APPID: *LOCAL.DB2.111126055301 
EDUID   : 41                   EDUNAME: db2shred (HDRLNX) 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrGetBlock, probe:40100 
MESSAGE : Log page checksum mismatch. pageLsn 0001DBC66FFB 
 
2011-11-26-04.02.07.349893-300 I398635E474         LEVEL: Error 
PID     : 1593                 TID  : 140118379718400PROC : 
db2sysc 
INSTANCE: svtdbm               NODE : 000          DB   : HDRLNX 
APPHDL  : 0-8                  APPID: *LOCAL.DB2.111126055301 
EDUID   : 39                   EDUNAME: db2redom (HDRLNX) 
FUNCTION: DB2 UDB, recovery manager, sqlpPRecReadLog, probe:1275 
RETCODE : ZRC=0x87800148=-2021654200=HDR_ZRC_BAD_LOG 
          "HADR standby found bad log"
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* HADR users on all platforms                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Without the fix, customer could be exposed to the problem    * 
* described in the APAR error description                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v95fp9                                            * 
****************************************************************
Local-Fix:
Manually copy the log file for which the log page checksum was 
reported from Primary to Standby and restart the standby.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
The fix is delivered db2_v95fp9. Customers will not see the 
checksum error on standby with the fix.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC80600 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.12.2011
07.03.2012
08.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP9
Problem behoben lt. FixList in der Version
9.5.0.9 FixList