DB2 - Problembeschreibung
Problem IC97725 | Status: Geschlossen |
HDR_ZRC_BAD_LOG AND HADR: MISSING LOG ON PRIMARY AFTER TAKEOVER | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
After a take over and reactivation (deactivate database followed by activate database) on the new HADR Standby, DB2 might fail with the following errors if log archive is not shared between the Primary and Standby: FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduS, probe:21210 MESSAGE : HADR: Missing log on primary. Standby shutting down and FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrEduS, probe:21210 RETCODE : ZRC=0x87800148=-2021654200=HDR_ZRC_BAD_LOG "HADR standby found bad log" This can happen in the following scenario: 1. Primary fills up Log A and part of Log B. Log A has been backed up on Primary. Standby does not have Log A in the archive. Standby and Primary do not share archive so the logs archived in one machine are not seen by the other. 2. Standby issues a Take over. Current log position at time of Role Switch is Log B. 3. Log B in old Primary was partially written. 4. The new Standby database is deactivated and then activated after the take over. 5. The new Standby will try to retrieve the log B from the archive as it is "stale" and in this case it does not find it: Messages in the db2diag.log on the new Standby: Extent B in log path may be stale. Trying archive. FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, probe:5120 MESSAGE : Return code for LFR opening file B was -2146434659 --------> SQLP_LOG_NOT_IN_ARCHIVE 4. RCUStartLso goes back to last page of Log A. As the new Primary (old Standby) does not have it, the new standby fails with : MESSAGE : HADR: Missing log on primary. Standby shutting down | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 and Fix Pack 10 * **************************************************************** | |
Local-Fix: | |
Workaround is to move the missing log A to the new Primary. As this has been processed already it should continue correctly. | |
Lösung | |
Problem was first fixed in DB2 Version 9.7 and Fix Pack 10 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 18.11.2013 10.11.2014 10.11.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7. | |
Problem behoben lt. FixList in der Version | |
9.7.0.10 |