DB2 - Problembeschreibung
Problem IC68989 | Status: Geschlossen |
HADR may disconnect with 'HADR_TIMEOUT' message after system clock is set backwards. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problembeschreibung: | |
When HADR is running, if the system clock is set backwards by any amount (even less than a second), there is a chance that HADR will disconnect with a message similar to the following in the diag.log: 2010-05-25-06.15.21.808743-240 I23270A490 LEVEL: Error PID : 23818 TID : 1 PROC : db2hadrs (XXXXXXX) 0 INSTANCE: db2xxxxx NODE : 000 FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduAcceptEvent, probe:20200 MESSAGE : Did not receive anything through HADR connection for the duration of HADR_TIMEOUT. Closing connection. DATA #1 : Hexdump, 4 bytes 0xFFFFFFFF7FFFD174 : FFFF FFFF A high entry like 'FFFF FFFF' strongly suggests that this problem has happened. It is possible that the system clock was set backwards by an automated system-clock maintenance process (such as xntpd). You can look for entries in system logs like /var/log/messages for time changes around any 'HADR_TIMEOUT' disconnection. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * When HADR is running, if the system clock is set backwards * * by * * any amount (even less than a second), there is a chance that * * * * HADR will disconnect with a message similar to the following * * in * * the diag.log: * * * * * * * * 2010-05-25-06.15.21.808743-240 I23270A490 LEVEL: * * Error * * PID : 23818 TID : 1 PROC : * * * * db2hadrs (XXXXXXX) 0 * * * * INSTANCE: db2xxxxx NODE : 000 * * * * FUNCTION: DB2 UDB, High Availability Disaster Recovery, * * * * hdrEduAcceptEvent, probe:20200 * * * * MESSAGE : Did not receive anything through HADR connection * * for * * the duration of * * * * HADR_TIMEOUT. Closing connection. * * * * DATA #1 : Hexdump, 4 bytes * * * * 0xFFFFFFFF7FFFD174 : FFFF FFFF * * * * * * * * A high entry like 'FFFF FFFF' strongly suggests that this * * * * problem has happened. * * * * * * * * It is possible that the system clock was set backwards by an * * * * automated system-clock maintenance process (such as xntpd). * * You * * can look for entries in system logs like /var/log/messages * * for * * time changes around any 'HADR_TIMEOUT' disconnection * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 9.7 version Fix Pack 10. * **************************************************************** | |
Local-Fix: | |
If the HADR pair does not automatically reconnect, deactivate the database and reactivate it. | |
verfügbare FixPacks: | |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows | |
Lösung | |
Problem was first fixed in Version 9.1 Fix Pack 10. | |
Workaround | |
If the HADR pair does not automatically reconnect, deactivate the database and reactivate it. | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC72329 IC72330 IC72334 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 04.06.2010 23.06.2011 23.06.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.1.FP10, 9.7. | |
Problem behoben lt. FixList in der Version | |
9.1.0.10 |