| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC84533 | Status: Closed |
IN SUPER ASYNC MODE, HADR STANDBY COULD CRASH IN LOCAL CATCHUP STATE AFTER DEACTIVATING PRIMARY DATABASE | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
For HADR database in supersync mode, when primary is deactivated gracefully in local catchup state, HADR standby could be crashed. On primary, the below message will be printed to db2diag.log: 2012-03-18-01.59.00.354402-420 I2061400E373 LEVEL: Warning PID : 7405 TID : 47028109306176PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : DBNAME EDUID : 30 EDUNAME: db2hadrp (DBNAME) FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduP, probe:20694 MESSAGE : Sending hard checkpoint XHDR. On standby, below messages will appear in db2diag.log: 2012-03-19-18.25.22.115785-420 I76441E457 LEVEL: Info PID : 19997 TID : 47368376412480PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : TESTDB EDUID : 63 EDUNAME: db2hadrs (TESTDB) FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrHandleXhdrMsg, probe:10175 DATA #1 : <preformatted> Received HDR_MSG_XHDRCLOSE, ExtNum 4, firstLso 41045321 ExtSize 4, PageCount 2, state 0x8001 2012-03-19-18.25.22.314115-420 I76899E479 LEVEL: Severe PID : 19997 TID : 47368376412480PROC : db2sysc INSTANCE: db2inst1 NODE : 000 DB : TESTDB EDUID : 63 EDUNAME: db2hadrs (TESTDB) FUNCTION: DB2 UDB, RAS/PD component, pdResilienceIsSafeToSustain, probe:800 DATA #1 : String, 37 bytes Trap Sustainability Criteria Checking DATA #2 : Hex integer, 8 bytes 0x200000000000800C DATA #3 : Boolean, 1 bytes false | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 LUW HADR users using SUPERASYNC on all platforms * **************************************************************** * PROBLEM DESCRIPTION: * * Without the fix, customer could hit the problem described * * in the error description * **************************************************************** * RECOMMENDATION: * * Upgrade to v101fp1. * **************************************************************** | |
| Local Fix: | |
One way to avoid running into this issue is to make sure that primary is deactivated only after standby finishes local catchup. If in case Standby ran into the issue then restarting the standby database should bring the standby database back to normal. | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
| Solution | |
After applying v101fp1,the problem in error description can be avoided. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.06.2012 06.12.2012 06.12.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.1 |
|
| 10.5.0.1 |
|