DB2 - Problem description
| Problem IC68184 | Status: Closed |
DURING REMOTE CATCHUP, STANDBY MAY HANG INDEFINITELY IF PRIMARY COULD NOT FIND A LOG. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
During normal operation, an HADR Standby requests logs from the
HADR Primary while in 'Remote Catchup' state. If the requested
logs are not available on the Primary then the Standby will shut
down. In rare, random, cases the Standby may hang during its
shut down.
Typical db2diag.log messages that you would see on the Standby
server:
2010-03-17-23.01.21.363452-300 I139143A368 LEVEL: Error
PID : 692376 TID : 8997 PROC : db2sysc
0
INSTANCE: db2p51 NODE : 000
EDUID : 8997 EDUNAME: db2hadrs (P51) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduS,
probe:21210
MESSAGE : HADR: Missing log on primary. Standby shutting down
2010-03-17-23.01.21.363657-300 I139512A398 LEVEL: Error
PID : 692376 TID : 8997 PROC : db2sysc
0
INSTANCE: db2p51 NODE : 000
EDUID : 8997 EDUNAME: db2hadrs (P51) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduS,
probe:21210
RETCODE : ZRC=0x87800148=-2021654200=HDR_ZRC_BAD_LOG
"HADR standby found bad log"
2010-03-17-23.01.21.363808-300 I139911A342 LEVEL: Warning
PID : 692376 TID : 8997 PROC : db2sysc
0
INSTANCE: db2p51 NODE : 000
EDUID : 8997 EDUNAME: db2hadrs (P51) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduS,
probe:20342
MESSAGE : Info: Standby Finished.
2010-03-17-23.01.21.588793-300 I146338A350 LEVEL: Warning
PID : 692376 TID : 8997 PROC : db2sysc
0
INSTANCE: db2p51 NODE : 000
EDUID : 8997 EDUNAME: db2hadrs (P51) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrEduEntry, probe:21145
MESSAGE : Waiting for hdrEDUTerminate
Even though we see 'Standby Finished' message in db2diag.log, we
would still see db2hadrs thread running, which can be confirmed
using the
'db2pd -edus' command. The rest of the threads like db2shred,
db2redow,
db2redom will have exited.
Typical stack trace for db2hadrs thread would look like:
<StackTrace>
-------Frame------ ------Function + Offset------
0x09000000000D6FD8 thread_wait + 0x98
0x090000000557A90C sqloWaitEDUWaitPost + 0x1A4
0x0900000007312C24 @146@hdrEduEntry__FPcUi + 0x250
0x090000000549AD7C sqloEDUEntry + 0x1C
</StackTrace> | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users of DB2 High Availability Disaster Recovery (HADR) * **************************************************************** * PROBLEM DESCRIPTION: * * The HADR Standby hangs during a shut down (deactivation). * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.7 Fixpack 3. * **************************************************************** | |
| Local Fix: | |
db2_kill | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
The HADR Standby won't hang during shut down. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.04.2010 19.10.2010 19.10.2010 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.3 |
|
| 9.7.0.3 |
|