IBM Support

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

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error 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.
    

Local fix

  • Update the db2nodes.cfg file to contain the OS hostname value.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 105 Fix Pack 9                                *
    ****************************************************************
    

Problem conclusion

  • First Fixed in DB2 105 Fix Pack 9
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT17913

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-11

  • Closed date

    2017-09-27

  • Last modified date

    2017-09-27

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IT18607

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA50 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 10.5

Reference #: IT17913

Modified date: 27 September 2017