|
Problem IC80590
|
Status: Closed |
DB2 HADR STANDBY COULD BE BROUGHT DOWN AFTER TAKEOVER OPERATION IN SUPER ASYNC MODE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
HADR standby could be brought down on receiving the first log
page after a takeover due to standby being at wrong position in
log stream.
This will happen only at a specific scenario where a takeover is
issued when the old primary wrote a partial page with one free
byte.
The DB2 diaglog on standby will contain diagnostic messages
similar to the below ones:
2011-12-23-01.11.32.840859-480 I5466492E484 LEVEL: Error
PID : 24906 TID : 47433094523200PROC :
db2sysc
INSTANCE: db2inst1 NODE : 000
EDUID : 444 EDUNAME: db2hadrs (DBNAME)
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrAddDataBlock, probe:40012
MESSAGE : Primary/standby mismatch. RCUStartLSO 77692636 not on
record
boundary. RCU first page bytecount 162, firstIndex
130, pageLso
77692798.
Or:
2011-12-24-18.20.59.771695-480 I124574E542 LEVEL: Severe
PID : 20239 TID : 47073726556480PROC :
db2sysc
INSTANCE: db2inst1 NODE : 000
EDUID : 53 EDUNAME: db2hadrs (DBNAME)
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>
diffPage 1 TailPage 0 does not match pagePso 41106566 and
firstLso 41102385 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 LUW HADR users on all platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* Without the fix, customer could hit the problem described *
* in the error description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v97fp6 *
**************************************************************** |
| Local Fix: |
restart standby by "db2 activate db hadrdb" |
| available fix packs: |
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 |
After applying v97fp6, the problem in error description can be
avoided. Standby will not be brought down after takeover even
with the condition described in error description. |
| Workaround |
restart standby once hit the problem |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.12.2011
05.06.2012
05.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
