DB2 - Problembeschreibung
Problem IT06504 | Status: Geschlossen |
HADR TAKES A LONG TIME TO FAILOVER TO THE STANDBY WHEN THE DB2ST AR2 BINARY IS RENAMED AND THE DB2SYSC IS KILLED ON THE PRIMARY | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
In a HADR HA(TSA) environment, if either the db2start or db2star2 binary is renamed on the primary server and the db2sysc process is then killed. It can take longer than expected (~1-3 minutes) for the HADR database to failover to the standby server. Depending on the database's HADR_PEER_WINDOW value, this delay may cause the failover to fail due to the peer window having expired. If this occurs, the following error message can be seen in the standby server's db2diag.log: 2014-12-26-10.57.52.425048-360 I28769E434 LEVEL: Warning PID : 21248 TID : 140736813065984 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : HADRDB HOSTNAME: db2host1 EDUID : 61 EDUNAME: db2hadrs.0.0 (HADRDB) 0 FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduAcceptEvent, probe:20202 MESSAGE : Peer window ends. Peer window expired. In this test scenario, the HADR database should be able to quickly (under 1 minute) failover to the standby server ensuring that the HADR peer window does not expire. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 Fix Pack 7 * **************************************************************** | |
Local-Fix: | |
Increase the database's HADR_PEER_WINDOW value or otherwise contact IBM support for a fix. | |
Lösung | |
First Fixed in DB2 10.5 Fix Pack 7 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 14.01.2015 09.05.2017 09.05.2017 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.7 |