DB2 - Problembeschreibung
Problem IC96568 | Status: Geschlossen |
RUNNING "DB2HAICU -DISABLE" DOES NOT UNSET THE "CLUSTER MANAGER"DBM CFG VALUE IF A CLUSTER DOMAIN DOES NOT EXIST. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
In the case where a high availability environment has been setup using the db2haicu utility and the TSA cluster domain has been deleted using TSA native commands, i.e. the "rmrpdomain" command, the "Cluster manager" DBM CFG parameter will be left set with value "TSA". This behavior is working as designed. In this case, we expect the user to unset the "Cluster manager" DBM CFG value by running the "db2haicu -disable" command. The issue is that the "db2haicu -disable" command fails with the following error and as a result does not unset the "Cluster manager" DBM CFG value: [db2inst1@db2host1 ~/CLUSTER_MGR_v101]: db2haicu -disable Welcome to the DB2 High Availability Instance Configuration Utility (db2haicu). You can find detailed diagnostic information in the DB2 server diagnostic log file called db2diag.log. Also, you can use the utility called db2pd to query the status of the cluster domains you create. For more information about configuring your clustered environment using db2haicu, see the topic called 'DB2 High Availability Instance Configuration Utility (db2haicu)' in the DB2 Information Center. db2haicu determined the current DB2 database manager instance is 'pstedman'. The cluster configuration that follows will apply to this instance. Are you sure you want to disable high availability (HA) for the database instance 'db2inst1'. This will lock all the resource groups for the instance and disable the HA configuration parameter. The instance will not failover if a system outage occurs while the instance is disabled. You will need to run db2haicu again to enable the instance for HA. Disable HA for the instance 'db2inst1'? [1] 1. Yes 2. No 1 Query failed. Refer to db2diag.log for the current member and the DB2 Information Center for details. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All db2haicu users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to 10.5.0.3 * **************************************************************** | |
Local-Fix: | |
Setup a highly availability environment using the db2haicu utility and proceed to delete it by issuing the "db2haicu -delete" command. This sequence of events will unset the "Cluster manager" DBM CFG value. | |
verfügbare FixPacks: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Problem Fixed In 10.5.0.3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 02.10.2013 03.03.2014 03.03.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.3 | |
10.5.0.3 |