IC92342: UPDATING A MEMBER OR CF TO ADD A NETWORK INTERFACE LOSES THAT UPDATED AFTER A REBOOT OR FAILOVER

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When updating a member with an additional network interface e.g.
    using :
    
     db2iupdt -add -m pocm0 -mnet pocm0-ib0,pocm0-ib1  -i db2ssh1
    db2sdin1
    
    the db2nodes.cfg will be updated with the additional netname
    reflected in the db2instance -list output :
    
    db2sdin1@pocm0$ db2instance -list
    
    ID        TYPE             STATE                HOME_HOST
    CURRENT_HOST            ALERT   PARTITION_NUMBER
    LOGICAL_PORT    NETNAME
    --        ----             -----                ---------
    ------------            -----   ----------------
    ------------    -------
    0       MEMBER           STARTED                    pocm0
    pocm0               NO                  0                   0
    pocm0-ib0,pocm0-ib1
    1       MEMBER           STARTED                    pocm1
    pocm1               NO                  0                   0
    pocm1-ib0,pocm1-ib1
    2       MEMBER           STARTED                    pocm2
    pocm2               NO                  0                   0
    pocm2-ib0,pocm2-ib1
    128     CF               PRIMARY                   poccf1
    poccf1               NO                  -                   0
    poccf1-ib0,poccf1-ib1
    129     CF                  PEER                   poccf2
    poccf2               NO                  -                   0
    poccf2-ib0,poccf2-ib1
    
    The problem in this apar is that this information is not
    permanently stored in the HA registry file which can be viewed
    using db2hareg -dump :
    
    ...
    NL,0,pocm0,0,pocm0-ib0,-,MEMBER
    NL,1,pocm1,0,pocm1-ib0,-,MEMBER
    NL,2,pocm2,0,pocm2-ib0,-,MEMBER
    ...
    
    -> only 1 netname is listed.
    
    As a result, when there is a reboot or a failback after a
    failover , the member or the Cluster Caching Facility which
    previously had the netname added, will lose this information.
    

Local fix

  • Instead of updating a member or CF , drop and add the member or
    CF  as follows
    :
    db2iupdt -drop -m pocm0
    db2iupdt -add -m pocm0 -mnet pocm0-ib0,pocm0-ib1 -i db2ssh1
    db2sdin1
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Purescale users.                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade the database server to V10.1 Fix Pack 3              *
    ****************************************************************
    

Problem conclusion

  • This problem was first fixed in DB2 V10.1 Fix Pack 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC92342

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-16

  • Closed date

    2013-10-21

  • Last modified date

    2013-10-21

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

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA10 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

10.1

Reference #:

IC92342

Modified date:

2013-10-21

Translate my page

Machine Translation

Content navigation