IC95979: HADR STANDBY LOSES CONNECTION AND RECONNECTS FOLLOWING A GRACEFUL TAKEOVER WHEN SUPERASYNC IS USED FOR HADR_SYNCMODE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Right after a graceful takeover is issued, the new hadr standby
    loses connection and reconnects. This failure is seen when
    superasync mode is used for
    the HADR pair. The problem may not be very common. When the
    problem reproduces, similar to the following diagnostic data
    will be seen in the DB2 db2diag.log
    
    2013-08-29-01.38.40.836081-240 I710579A654          LEVEL:
    Severe
    PID     : 27328552             TID : 10025          KTID :
    46727219
    PROC    : db2sysc
    INSTANCE: tnarayan             NODE : 000           DB   :
    MSDBDR
    HOSTNAME: coralpib65
    EDUID   : 10025                EDUNAME: db2hadrs.0.0 (MSDBDR)
    FUNCTION: DB2 UDB, data protection services, sqlpgWriteToDisk,
    probe:909
    MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File
    cannot be used"
              DIA8414C Logging can not continue due to an error.
    DATA #1 : <preformatted>
    TailPage 790 does not match pagePso 30942925468 and firstLso
    30939693201.
    lowLso: 30942913241, highLso: 30942917317
    

Local fix

  • Please upgrade to DB2 version 10.5 Fixpack 3.
    If the problem is reproduced before the upgrade is applied,
    restarting HADR will fix the issue. After the restart the pair
    will connect successfully and standby will catchup with primary
    from the correct position.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL DB2 LUW HADR users using superasync synchronization mode *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 LUW Version 10.5 Fixpack 3                    *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 LUW version 10.5 Fixpack 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC95979

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-09-16

  • Closed date

    2014-09-08

  • Last modified date

    2014-09-08

  • 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

  • RA50 PSN

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

10.5

Reference #:

IC95979

Modified date:

2014-09-08

Translate my page

Machine Translation

Content navigation