DB2 - Problembeschreibung
Problem IC64739 | Status: Geschlossen |
DB2 HADR STANDBY CAN LOOSE TRACK OF ARCHIVED LOGS AFTER TAKEOVER BY FORCE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problembeschreibung: | |
Under the following circumstances DB2 HADR STANDBY can loose track of archived logs after a TAKEOVER BY FORCE: - serious (HW) problems with primary database server. - takeover by force and the standby becomes the new primary. - old primary is defect and cannot be used as standby anymore. - "stop hadr" command on new primary so it becomes a standard server. - ONLINE BACKUP with INCLUDE LOGS options A backup with INCLUDE LOGS triggers LOG ARCHIVE, but DB2 starts with S0000000.LOG, ie. the very old (first) log file ever, which of course is not available anymore. | |
Problem-Zusammenfassung: | |
USERS AFFECTED All using HADR PROBLEM DESCRIPTION see ERROR DESCRIPTION PROBLEM SUMMARY see ERROR DESCRIPTION | |
Local-Fix: | |
n/a | |
verfügbare FixPacks: | |
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows | |
Lösung | |
The complete fix for this problem first appears in DB2 UDB Version 9.1 FixPak 9. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC64742 IC64747 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 23.11.2009 14.04.2010 14.04.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.0., 9.1. | |
Problem behoben lt. FixList in der Version | |
9.1.0.9 |