DB2 - Problembeschreibung
Problem IC64729 | Status: Geschlossen |
ADDING AN INVALID MSCS DB2 RESOURCE CAUSES THE CLUSTER ADMINISTRATOR TO FAILS. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
Problem that we have seen is that the windows cluster resource group appears to be very unstable and can cause the cluster administrator to fail and no longer work. As a result the entire ms cluster\s fail. All that is needed is to create a new resource using the 'DB2 Server' resource type in an already predefined cluster group. The name of the resource needs to be an invalid instance name. Upon pressing next you will be notified that the instance does not exist. If you press ok to abort, it appears to create the definition and expects the instance to exist. Since the instance does not exist, it crashes the ms cluster and any restart fails. The only method I've found so far to resolve this is to create the instance that was in error and allow the ms cluster to restart. Once started you can then delete the offending resources. | |
Problem-Zusammenfassung: | |
ADDING AN INVALID MSCS DB2 RESOURCE CAUSES THE CLUSTER ADMINISTRATOR TO FAILS. | |
Local-Fix: | |
Workaround: Create the an instance for the problem resource and can then look to drop resource & then instance. | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in Version 9.5 Fix Pack 6 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC64730 IC66403 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 23.11.2009 17.05.2010 17.05.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP6 | |
Problem behoben lt. FixList in der Version |