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 IC90952 Status: Geschlossen

HADR standby database encounters log page checksum error

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
HADR standby database encounters log page checksum error, then 
shuts itself down. 
 
You may see the following messages in db2diag: 
 
2013-02-09-03.32.13.993712-300 I8918A544            LEVEL: Error 
PID     : 45940956             TID : 5541           PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 5541                 EDUNAME: db2lfr.0 (sample) 0 
FUNCTION: DB2 UDB, High Availability Disaster Recovery, 
hdrGetBlock, probe:40100 
MESSAGE : ZRC=0x87800148=-2021654200=HDR_ZRC_BAD_LOG 
          "HADR standby found bad log" 
DATA #1 : <preformatted> 
Log page checksum mismatch. pageLso 4258712948508, CheckSum 
118415316 
 
 
2013-02-26-20.31.53.315457-300 I12190A500           LEVEL: 
Warning 
PID     : 12714058             TID : 5656           PROC : 
db2sysc 0 
INSTANCE: vpcinp01             NODE : 000 
EDUID   : 5656                 EDUNAME: db2lfr.0 (VPCDB) 0 
FUNCTION: DB2 UDB, recovery manager, sqlplfrVerifyLogPages, 
probe:500 
DATA #1 : <preformatted> 
LFR Scan Num            = 4 
LFR Scan Caller's EDUID = 17992 
Checksum error when reading page 140870 from log file 
S0003158.LOG
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users on DB2 v101 FP2 and earlier                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V101 FP3                                      * 
****************************************************************
Local-Fix:
As a temporary workaround: 
 
1. Identify the affected logs from db2diag.log 
2. Deactivate standby database 
3. Copy over affected logs from primary database or archive 
location to standby database log path. 
4. Re-activate standby database
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First Fixed in Db2 v101 FP3.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC95369 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
19.03.2013
18.10.2013
18.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList