IC93799: DB2GCF UTILITY UPDATES THE DB2NODES.CFG TO SHORT HOSTNAME INSTEAD OF FULLY QUALIFIED HOST NAME

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • During a TSA automated database partition failover, db2gcfg
    updates the db2nodes.cfg file. In some cases this will be
    updated
    to the short name of the host instead of the fully qualified
    hostname.
    Example:
    
    $ cat db2nodes.cfg
    
    0 test04.torolab.ibm.com 0
    1 test04.torolab.ibm.com 1
    
    $ hostname (Run from test03)
    test03.torolab.ibm.com
    
    $ hostname (Run from test04)
    test04.torolab.ibm.com
    
     Online IBM.ResourceGroup:db2_db2inst1_0-rg Nominal=Online
            '- Online IBM.Application:db2_db2inst1_0-rs
                    |- Offline
    IBM.Application:db2_db2inst1_0-rs:test03
                    '- Online
    IBM.Application:db2_db2inst1_0-rs:test04
    Online IBM.ResourceGroup:db2_db2inst1_1-rg Nominal=Online
            '- Online IBM.Application:db2_db2inst1_1-rs
                    |- Offline
    IBM.Application:db2_db2inst1_1-rs:test03
                    '- Online
    IBM.Application:db2_db2inst1_1-rs:test04
    Online IBM.Equivalency:db2_db2inst1_0-rg_group-equ
            |- Online IBM.PeerNode:test04:test04
            '- Online IBM.PeerNode:test03:test03
    Online IBM.Equivalency:db2_db2inst1_1-rg_group-equ
            |- Online IBM.PeerNode:test04:test04
            '- Online IBM.PeerNode:test03:test03
    
    In the above setup, if I then run the "rgreq -o move
    db2_db2inst1_1-rg" command as root, it will cause TSA to
    failover database partition 1 from host test04 to ceha03. This
    works, but the problem is that the db2nodes.cfg file is being
    updated with the short hostname as seen below
    :
    
    $ cat db2nodes.cfg
    
    0 test04.torolab.ibm.com 0
    1 test03 0 ceha03
    
    The correct behavior would be for the DBM to update the 2nd line
    of the db2nodes.cfg as follows:
    
    1 test03.torolab.ibm.com 0 ceha03.torolab.ibm.com
    
    This is because the hosts OS hostname value is set to
    'test03.torolab.ibm.com'.
    

Local fix

Problem summary

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

Problem conclusion

  • Problem was first fixed in DB2 Version 9.7 and Fix Pack 9
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC93799

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-28

  • Closed date

    2013-12-17

  • Last modified date

    2013-12-17

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

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

    IC95450 IC95646

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

9.7

Reference #:

IC93799

Modified date:

2013-12-17

Translate my page

Machine Translation

Content navigation