DB2 - Problem description
Problem IC70851 | Status: Closed |
CANNOT REINTEGRATE OLD HADR PRIMARY AS STANDBY IF OLD PRIMARY WAS SHUTDOWN GRACEFULLY IN DISCONNECTED_PEER STATE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
If a clean database shutdown (deactivate db or db2stop) of the HADR Primary is performed while it is in DISCONNECTED_PEER state, and if the HADR Standby has successfully completed a 'takeover by force peer window only' command, then the old primary cannot reintegrate as a standby. By design, if the 'takeover' command is issued while the Standby database is in DISCONNECT_PEER state, and if the Primary is terminated (by a db2_kill for example) while still in DISCONNECTED_PEER, then primary reintegration should always succeeed. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Customer using the HADR feature * **************************************************************** * PROBLEM DESCRIPTION: * * Cannot re-integrate old primary if it was shutdown * * gracefully in the disconnected_peer state. * **************************************************************** * RECOMMENDATION: * * Upgrade to v97_fp4 and above. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fixpack 4 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.08.2010 16.05.2011 16.05.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4, 9.7._FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |