DB2 - Problembeschreibung
Problem IT00975 | Status: Geschlossen |
NEW "DB2CLUSTER -CM -DELETE -RESOURCES -FORCE" OPTION USED TO DELETE THE HA REGISTRY METADATA | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
In a pureScale environment, when we delete the resource model using the "db2cluster -cm -delete -resources" command, and then try to repair the resource model by running the "db2cluster -cm -repair -resources" command, it will attempt to create the cluster manager resources but fail because it does not find the HA registry metadata. Because of this, we end up having to manually edit the db2nodes.cfg file and re-creating the cluster manager resources manually. To avoid this problem the following modifications have been made: 1) The "db2cluster -cm -delete -resources" command will now fail if there is a mismatch between the HA registry metadata and the contents of the db2nodes.cfg file. The "db2cluster -cm -delete -resources -force" command can be used to override this check and delete the HA resource model and the HA registry contents in this case. 2) The "db2cluster -cm -repair -resources" command will now fail if the HA registry metadata does not exist. 3) The "db2cluster -cm -create -resources" command will now fail if the HA registry metadata already exists. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Purescale users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V10.5 FP4 * **************************************************************** | |
Local-Fix: | |
N/A | |
Lösung | |
Fixed in DB2 V10.5 FP4 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 10.04.2014 06.10.2014 16.07.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |