IBM Support

IT21553: THE PRIMARY HADR DATABASE FAILS OVER TO THE STANDBY AFTER CONFIGURING FOR HA VIA DB2HAICU.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When configuring an HADR database pair for HA via the db2haicu
    utility, it is possible that the Primary HADR database role
    fails over to the standby host shortly after db2haicu execution.
    
    If this problem occurs and the following two db2diag.log
    messages are seen on the original standby host, then it is a
    match for this APAR:
    
    2017-06-25-02.18.03.915829+720 E80421950E389         LEVEL: Info
    PID     : 2695                 TID : 48009457543904  PROC :
    db2gcf
    INSTANCE: db2inst1               NODE : 000
    HOSTNAME: hostB
    FUNCTION: DB2 UDB, high avail services, sqlhaRemoveFlagRG,
    probe:673
    MESSAGE : Resource flag file has been deleted
    DATA #1 : String, 49 bytes
    db2_HADRDB_hostA_Reintegrate_db2inst1_db2inst1
    
    2017-06-25-02.18.03.977507+720 E80422340E393         LEVEL: Info
    PID     : 2695                 TID : 48009457543904  PROC :
    db2gcf
    INSTANCE: db2inst1               NODE : 000
    HOSTNAME: hostB
    FUNCTION: DB2 UDB, high avail services, sqlhaCreateFlagRG,
    probe:508
    MESSAGE : IBM.Test flag resource has been created
    DATA #1 : String, 49 bytes
    db2_HADRDB_hostA_Reintegrate_db2inst1_db2inst1
    
    The root cause for this issue is the
    'db2_HADRDB_hostA_Reintegrate_db2inst1_db2inst1' file being left
    over in /tmp on the standby host.
    

Local fix

  • Before you run db2haicu to configure HA, first ensure that there
    are no leftover flag files in /tmp on either host, i.e. run the
    "ls /tmp | grep db2_<DBNAME>" command on both hosts and ensure
    there are no files with this prefix. If there are, they must be
    deleted.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher               *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 3 Fix Pack 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT21553

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-21

  • Closed date

    2018-03-19

  • Last modified date

    2018-03-19

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

    IT21424

  • 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

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
19 March 2018