DB2 FOR LUW / DB2FORLUW / 950 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 9.5 FP9                                           * 
****************************************************************

Update the localHost and remoteHost parameters in both XML files 
such that they are set correctly.

DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem first fixed in 9.5 FP9

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC79216 IC84163 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

26.09.2011
07.05.2012
07.05.2012

9.5.FP9