IBM Support

IC69349: REBOOT HADR STANDBY DATABASE ALSO REBOOT PRIMARY DATABASE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The TieBreaker is tested every 30 seconds to ensure the server
    continues to have connectivity. It appears there was a lose of
    connectivity or maybe some latency that caused the quorum state
    to change to PENDING_QUORUM.  The most likely reason the reboot
    occurred is because the periodic check of the network TieBreaker
    failed to be able to ping the remote device. Lets assume that it
    was a momentarily ping failure because of network latency or
    short network glitch. To avoid these small network issues from
    forcing an unnecessary loss in quorum, increase the retry count
    for the network TieBreaker. The default retry count is 2. The
    maximum retry count is 9.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * db2haicu integrated HA solution users                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The TieBreaker is tested every 30 seconds to ensure the      *
    * server                                                       *
    * continues to have connectivity. It appears there was a lose  *
    * of                                                           *
    * connectivity or maybe some latency that caused the quorum    *
    * state                                                        *
    * to change to PENDING_QUORUM.  The most likely reason the     *
    * reboot                                                       *
    * occurred is because the periodic check of the network        *
    * TieBreaker                                                   *
    * failed to be able to ping the remote device. Lets assume     *
    * that it                                                      *
    * was a momentarily ping failure because of network latency or *
    *                                                              *
    * short network glitch. To avoid these small network issues    *
    * from                                                         *
    * forcing an unnecessary loss in quorum, increase the retry    *
    * count                                                        *
    * for the network TieBreaker. The default retry count is 2.    *
    * The                                                          *
    * maximum retry count is 9.                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 V9.7 FP3                                      *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IC69349

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-06-18

  • Closed date

    2010-09-20

  • Last modified date

    2010-09-20

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

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

    IC77547

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSY

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC69349

Modified date: 20 September 2010