suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT17913 Status: Closed

DB2GCF MIGHT INCORRECTLY REPORT INSTANCE AS OPERABLE INSTEAD OF AVAILABLE
WHEN USING VIRTUAL HOSTNAME IN DB2NODES.CFG

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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.
available fix packs:
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 105 Fix Pack 9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.11.2016
27.09.2017
27.09.2017
Problem solved at the following versions (IBM BugInfos)
9.0.
Problem solved according to the fixlist(s) of the following version(s)