home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC79216 Status: Geschlossen

UNINTENDED AUTOMATIC TAKEOVER DURING CLUSTER SETUP USING DB2HAICU

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
verfügbare FixPacks:
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

Lösung
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
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.10.2011
30.01.2012
30.01.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList