DB2 - Problembeschreibung
Problem IC76974 | Status: Geschlossen |
IMPROVE DB2HAICU RESPONSE TEXT, WHEN VIP IS ALREADY IN USE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
db2haicu (maintenance mode) gives following error for VIPs that are already in use: Select an administrative task by number from the list below: 1. Add or remove cluster nodes. 2. Add or remove a network interface. 3. Add or remove a highly available database. 4. Add or remove a mount point. 5. Add or remove an IP address. 6. Add or remove a non-critical path. 7. Change failover policy for this instance. 8. Create a new quorum device for the domain. 9. Destroy the domain. 10. Exit. Enter your selection: 5 Do you want to add or remove IP addresses to or from the cluster? [1] 1. Add 2. Remove Enter the virtual IP address: 10.128.199.225 The IP address 10.128.199.225 is already in use. Enter an IP address that is not used anywhere on the network for your high availability setup. The purpose of this APAR is to improve the given response message to explain that db2haicu is not allowed to create a TSA ServiceIP resource, when the associated IP alias is active. Deactivate the alias first, then run db2haicu again and add the TSA ServiceIP resource. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 6. * **************************************************************** | |
Local-Fix: | |
n/a | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 9.7 Fix Pack 6. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 15.06.2011 06.06.2012 06.06.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP6 | |
Problem behoben lt. FixList in der Version | |
9.7.0.6 |