|
Problem IC69349
|
Status: Closed |
REBOOT HADR STANDBY DATABASE ALSO REBOOT PRIMARY DATABASE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| 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. |
| 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 *
**************************************************************** |
| Local Fix: |
Refer to the following to manually specify option Count=9 to the
TieBreaker:
http://www-01.ibm.com/support/docview.wss?uid=swg21430001 |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Refer to the following to manually specify option Count=9 to the
TieBreaker:
http://www-01.ibm.com/support/docview.wss?uid=swg21430001 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC77547
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.06.2010
20.09.2010
20.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
