|
Problem IC79216
|
Status: Closed |
UNINTENDED AUTOMATIC TAKEOVER DURING CLUSTER SETUP USING DB2HAICU |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
To create an automated cluster controlled HADR environment,
customers should provide correct localHost and remoteHost
parameters for primary and standby XML files. However, some
customers may use the same XML file for both systems. In that
XML file, if localHost and remoteHost parameters point to
primary and standby hostnames respectively, db2haicu will
successfully complete the cluster setup. If we inverse the host
names in that XML file, DB2 will think that the primary is
supposed to be the standby and vice-versa which triggers an
automatic takeover on the standby and swaps the database roles. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* HADR setup integrated into a High Availability solution *
* (e.g. TSA) *
****************************************************************
* PROBLEM DESCRIPTION: *
* To create an automated cluster controlled HADR environment, *
* customers should provide correct localHost and remoteHost *
* parameters for primary and standby XML files. However, some *
* customers may use the same XML file for both systems. In *
* that XML file, if localHost and remoteHost parameters point *
* to primary and standby hostnames respectively, db2haicu will *
* successfully complete the cluster setup. If we inverse the *
* host names in that XML file, DB2 will think that the primary *
* is supposed to be the standby and vice-versa which triggers *
* an automatic takeover on the standby and swaps the database *
* roles. *
****************************************************************
* RECOMMENDATION: *
* Update the localHost and remoteHost parameters in both the *
* primary and the standby's XML files such that they are set *
* correctly. *
**************************************************************** |
| Local Fix: |
Update the localHost and remoteHost parameters in both XML files
such that they are set correctly. |
| 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 |
Fixed in DB2 v9.7fp6. Inversion of the localHost and remoteHost
parameters in the primary/standby XML files will no longer be
allowed; an error message will now be displayed specifying to
properly set the localHost and remoteHost parameters. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.10.2011
30.01.2012
30.01.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
|
 |
