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

STANDBY DATABASE STOPS AFTER RETRIEVING CERTAIN LOG FILES FROM PRIMARY
SERVER DUE TO LOG FILE HEADERS INCONSISTENCY

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If you have a HADR database and using Mirror Log Path and if the 
standby 
retrieves log files from the active log path on Primary and 
Mirror 
log files from archive DB2 might stop the standby due to log 
file header 
inconsistency error. 
 
db2diag.log messages may look as follows: 
 
2012-07-05-20.02.17.828075-420 I69901E529          LEVEL: 
Warning 
PID     : 18291                TID  : 46912937912640PROC : 
db2sysc 
INSTANCE: sfbao2               NODE : 000 
EDUID   : 57                   EDUNAME: db2hadrs (HADRDB) 
FUNCTION: DB2 UDB, data protection services, sqlpgole, 
probe:1200 
DATA #1 : <preformatted> 
Primary and mirror logpath log file headers are not consistent. 
Primary log file: 
'/nfshome/sfbao2/sfbao2/NODE0000/SQL00001/SQLOGDIR/S0000018.LOG' 
Mirror log file: '/nfshome/sfbao2/mirrorlog/S0000018.LOG' 
 
2012-07-05-20.02.17.833452-420 I70803E10725        LEVEL: Error 
PID     : 18291                TID  : 46912937912640PROC : 
db2sysc 
INSTANCE: xxxx               NODE : 000 
EDUID   : 57                   EDUNAME: db2hadrs (HADRDB) 
FUNCTION: DB2 UDB, data protection services, sqlpgole, 
probe:2880 
MESSAGE : Bad extent header: 
DATA #1 : Hexdump, 2048 bytes 
 
2012-07-05-20.02.17.835550-420 I81529E414          LEVEL: Error 
PID     : 18291                TID  : 46912937912640PROC : 
db2sysc 
INSTANCE: xxxx               NODE : 000 
EDUID   : 57                   EDUNAME: db2hadrs (HADRDB) 
FUNCTION: DB2 UDB, data protection services, sqlpgole, 
probe:2880 
MESSAGE : ExtNum = 
DATA #1 : Hexdump, 4 bytes 
0x00002AAAC4FFC598 : 1200 0000 
.... 
 
2012-07-05-20.02.17.837254-420 I81944E358          LEVEL: Error 
PID     : 18291                TID  : 46912937912640PROC : 
db2sysc 
INSTANCE: xxxx               NODE : 000 
EDUID   : 57                   EDUNAME: db2hadrs (HADRDB) 
FUNCTION: DB2 UDB, data protection services, sqlpgole, 
probe:2110 
MESSAGE : Error -2045771763 opening database log extent 18:
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms.                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
*                                                              * 
* A log file in mirror log path is created while HADR standby  * 
* prepares log file for writing and renamed from other file,   * 
* but the extent header                                        * 
* is not correct after renaming.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version v9.7 and Fix Pack 10 or Later         * 
****************************************************************
Local Fix:
Solution
Problem was first Fixed in DB2 Version 9.7 and Fix Pack 10.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.06.2013
10.11.2014
10.11.2014
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.10 FixList