DB2 - Problembeschreibung
Problem IT17913 | Status: Geschlossen |
DB2GCF MIGHT INCORRECTLY REPORT INSTANCE AS OPERABLE INSTEAD OF AVAILABLE WHEN USING VIRTUAL HOSTNAME IN DB2NODES.CFG | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
When using db2gcf to check the availability of an instance via the following command: db2gcf -s -i <instance> it may report the DB2 instance as "Operable" instead of "Available" if a virtual hostname is used in the db2nodes.cfg file. Here is the output of the dbgcf command in this case: $ db2gcf -s -i db2inst1 Instance : db2inst1 DB2 State : Operable If DIAGLEVEL is set to 4, then the following db2diag.log message will also be observed: 2016-11-10-20.17.08.221449-300 I2895E352 LEVEL: Info PID : 17988 TID : 140439091885856 PROC : db2gcf INSTANCE: db2inst1 NODE : 000 HOSTNAME: host1 FUNCTION: DB2 Common, Generic Control Facility, gcf_getstate, probe:2565 DATA #1 : String, 59 bytes db2inst1 , 0 : is not local and hence status not obtained. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 105 Fix Pack 9 * **************************************************************** | |
Local-Fix: | |
Update the db2nodes.cfg file to contain the OS hostname value. | |
verfügbare FixPacks: | |
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows | |
Lösung | |
First Fixed in DB2 105 Fix Pack 9 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 11.11.2016 27.09.2017 27.09.2017 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.0. | |
Problem behoben lt. FixList in der Version |