DB2 FOR LUW / DB2FORLUW / 950 - DB2

XML files can be used to create a single virtual IP(VIP). If 
attempting to add a second VIP, it will get added to the 
instance resource group rather than the HADR database resource 
group. 
 
Here's an example of an XML file with two VIP's. 
 
<HADRDBSet> 
<HADRDB databaseName="SAMPLE" localInstance="db2inst1" 
remoteInstance="db2inst1" localHost="amdha1" remoteHost="amdha2" 
/> 
<VirtualIPAddress baseAddress="192.00.000.58" 
subnetMask="255.255.255.0" networkName="db2_frontnet_0"/> 
<VirtualIPAddress baseAddress="192.00.130.45" 
subnetMask="255.255.255.0" networkName="db2_backnet_0"/> 
</HADRDBSet> 
 
In the above case, the db2_back_net_0 VIP would be incorrectly 
added to the instance resource group. The intended behavior is 
to allow multiple VIP's to be created as part of a single XML 
file and to correctly add them to the HADR database resource 
group.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2HAICU CANNOT CREATE MORE THAN ONE VIRTUAL IP USING XML    * 
* FILE                                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 9.5 FP9                                           * 
****************************************************************

Run db2haicu in XML mode, specifying a single VIP in the XML 
file. Once the HADR setup is complete, then proceed to add the 
second VIP in db2haicu maintenance mode.

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 on 9.5 FP9

Run db2haicu in XML mode, specifying a single VIP in the XML 
file. Once the HADR setup is complete, then proceed to add the 
second VIP in db2haicu maintenance mode.

forerunner  : APAR is sysrouted TO one or more of the following: IC79225 IC84166 
follow-up : 

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

04.10.2011
07.05.2012
07.05.2012

9.5.FP9