IBM Support

IT25993: WHEN THERE ARE MANY CONNECTIONS TO THE PRIMARY DATABASE, HADR TAKEOVER COULD RETURN SQL1770N RC7.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When there are many current and incoming connections to the HADR
    primary database, the takeover hadr command could sometime
    return SQL1770N rc7.
    
    During hadr takeover, the primary database has to force off
    current connections and block incoming connections from
    entering. When there are too
    
    many connections the process might take too long and eventually
    timeout, causing takeover to fail on the standby database.
    
    The following diagnostic message can be found in db2diag.log on
    standby:
    
    2018-08-13-15.25.14.245149-240 I4622014E613          LEVEL:
    Error
    
    PID     : 15112                TID : 139723221755648 KTID :
    27920
    
    PROC    : db2sysc 0
    
    INSTANCE: db2inst1             NODE : 000            DB   :
    TESTDB
    
    HOSTNAME: DB2INST1
    
    EDUID   : 409                  EDUNAME: db2hadrs.0.0 (TESTDB) 0
    
    FUNCTION: DB2 UDB, High Availability Disaster Recovery,
    hdrEduAcceptEvent, probe:20240
    
    DATA #1 : <preformatted>
    
    Standby has not received data from primary for 601 seconds.
    Check the status of the primary. Aborting TAKEOVER.
    
    hdrCurrentTime 1534188314 hdrLastLogRecvTime 1534187713
    hdrGracefulTkTimeout 600
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT25993

  • 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

    2018-08-16

  • Closed date

    2018-11-27

  • Last modified date

    2018-11-27

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

    IT25963

  • 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":"BU048","label":"IBM Software"},"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:
27 November 2018