IBM Support

IT06718: IN A TSA AUTOMATED HADR ENVIRONMENT, AN AUTOMATED HADR FAILOVER OCCURS IMMEDIATELY AFTER A MANUAL TAKEOVER HADR COMMAND IS RUN

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • When issuing a manual takeover from the HADR standby, the
    command returns successfully and the standby db becomes the new
    primary. However, immediately afterwards, TSA initiates a second
    takeover request and switches the new primary db back to a
    standby. The reason for this behavior may be that a
    ClusterInitiatedMove resource flag was not cleaned up and still
    exists in /tmp from a previous TSA takeover operation.
    
    If this is the case, then the following db2diag.log message
    should be seen on the standby host at the time that the manual
    HADR takeover command was issued:
    
    2013-09-26-14.17.39.603232-240 E1930E465           LEVEL: Event
    PID     : 2510                 TID  : 47851748976960PROC :
    db2sysc
    INSTANCE: db2inst1             NODE : 000          DB   : HADRDB
    APPHDL  : 0-15                 APPID:
    *LOCAL.db2inst1.130926181739
    AUTHID  : DB2USER1
    EDUID   : 554                  EDUNAME: db2agent (HADRDB)
    FUNCTION: DB2 UDB, base sys utilities,
    sqeDBMgr::StartUsingLocalDatabase, probe:13
    START   : Received TAKEOVER HADR command.
    
    Immediately after the above db2diag.log message, the following
    db2diag.log message should be seen:
    
    2013-09-26-14.17.41.260002-240 E2396E435           LEVEL:
    Warning
    PID     : 2510                 TID  : 47851748976960PROC :
    db2sysc
    INSTANCE: db2inst1             NODE : 000          DB   : HADRDB
    APPHDL  : 0-15                 APPID:
    *LOCAL.db2inst1.130926181739
    AUTHID  : DB2USER1
    EDUID   : 554                  EDUNAME: db2agent (HADRDB)
    FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure,
    sqlhaLockHADRResource, probe:181
    
    If this second db2diag.log message is not seen, then this issue
    is being hit. The cause is that the IBM.Test
    ClusterInitiatedMove resource flag was not properly cleaned up
    as part of a prior TSA automated HADR takeover.
    

Local fix

  • In order to confirm whether or not this flag still exists,
    verify the output of the following commands:
    export CT_MANAGEMENT_SCOPE=2
    lsrsrc IBM.Test | grep ClusterInitiatedMove
    
    and:
    
    ls /tmp | grep ClusterInitiatedMove
    
    If the ClusterInitiatedMove flag resource or file exists, it
    will need to be manually removed. In order to remove the flag
    resource, run the following command as root:
    export CT_MANAGEMENT_SCOPE=2
    rmrsrc -s "Name like '%ClusterInitiatedMove%'" IBM.Test
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * TSA automated HADR environment                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 9.7 FP11                                      *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT06718

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-01-23

  • Closed date

    2015-10-06

  • Last modified date

    2016-01-15

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

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

    IT09203 IT09204

Fix information

Applicable component levels

  • R970 PSN

       UP

  • RA10 PSN

       UP

  • RA50 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IT06718

Modified date: 15 January 2016