IC95669: TCP CONNECTIONS FROM NON-HADR DATABASE SOFTWARE TO THE STANDBY MIGHT ALTER THE HADR STATE AND STALL LOG SHIPPING ON THE PRIMARY

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When TCP connections are made to the HADR standby database by
    software other than HADR database software, the log shipping on
    primary database is stopped. There is a large gap between the
    PRIMARY_LOG_TIME and STANDBY_LOG_TIME values. However, the
    HADR_STATE element is incorrectly reported as being in PEER
    state. A non-forced takeover operation might be allowed and it
    might be successful, but the operation will also experience some
    data loss.
    
    The following is an example of what you might see if this error
    occurs:
    $ db2pd -db sample -hadr
    
    Database Member 0 -- Database SAMPLE -- Active
    
                    HADR_ROLE = PRIMARY
    
                   HADR_STATE = PEER
    
          HADR_CONNECT_STATUS = CONNECTED
     HADR_CONNECT_STATUS_TIME = 2013-07-17 15:53:13.671498
    (1374043993)
    
    PRIMARY_LOG_FILE,PAGE,POS = S0001326.LOG, 0, 62379237
    STANDBY_LOG_FILE,PAGE,POS = S0001326.LOG, 0, 62379105
          HADR_LOG_GAP(bytes) = 13
    
             PRIMARY_LOG_TIME = 2013-07-17 15:54:55.000000
    (1374044095)
             STANDBY_LOG_TIME = 2013-07-17 14:57:27.000000
    (1374040647)
    

Local fix

  • Deactivate and activate the standby database in order to ship
    the rest of the logs to the standby database for replay.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 HADR users                                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix    *
    * Pack 4) or higher.                                           *
    ****************************************************************
    

Problem conclusion

  • Fixed in DB2 Cancun Release 10.5.0.4(also known as Fix Pack 4)
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC95669

  • 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-02

  • Closed date

    2014-10-16

  • Last modified date

    2014-10-16

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

    IC94252

  • 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

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

10.5

Reference #:

IC95669

Modified date:

2014-10-16

Translate my page

Machine Translation

Content navigation