|
Problem IC64025
|
Status: Closed |
DB2_HADR_PEER_WAIT_LIMIT DOES NOT WORK PROPERLY DURING THE TRANSITION FROM REMOTE CATCHUP STATE TO PEER STATE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
We have a database configuration parameter HADR_TIMEOUT, which
does not break the primary out of peer state if the primary
keeps receiving heartbeat messages from the standby while
blocked until an HADR database has not received any message from
its partner for the HADR_TIMEOUT period.
Then, some transactions with log flush situation may be
blocked if log replay on the standby database is stuck on a
large operation such as load or reorganization and the HADR
component will still send heartbeat messages to the primary
database on normal schedule.
On the other hand, we have a registry variable
DB2_HADR_PEER_WAIT_LIMIT. When it is set, HADR primary database
will break out of peer state if logging on the primary database
has been blocked for the specified number of seconds by
DB2_HADR_PEER_WAIT_LIMIT.
After disconnection, the standby database will continue
replaying already received logs. Once received logs have been
replayed, the standby will reconnect to the primary. Upon
re-connection, normal state transition follows (first remote
catchup state, then peer state).
So the intention of DB2_HADR_PEER_WAIT_LIMIT registry variable
is to not block the primary database and it should be operated
properly during the transition from remote catchup state to peer
state (the transition is internally known as nearly-peer state). |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL HADR USER *
****************************************************************
* PROBLEM DESCRIPTION: *
* when the registry var hadr_peer_wait_limit was introduced, *
* it did not apply to the near peer state. the fix was povided *
* in v91 and merged into v97. *
****************************************************************
* RECOMMENDATION: *
* upgrade to the new fix pack *
**************************************************************** |
| Local Fix: |
Not available |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows
|
| Solution |
extend the applicability of peer wait limit var to near peer
state |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.10.2009
08.03.2010
08.03.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
