DB2 - Problembeschreibung
Problem IC84166 | Status: Geschlossen |
DB2HAICU CANNOT CREATE MORE THAN ONE VIRTUAL IP USING XML FILE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1 FP1 or subsequent fix pack * **************************************************************** | |
Local-Fix: | |
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. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
Problem First Fixed in DB2 Version 10.1 Fix Pack 1 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.06.2012 05.12.2012 05.12.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.1 | |
10.5.0.1 |