DB2 - Problembeschreibung
Problem IC65345 | Status: Geschlossen |
ROLLFORWARD FAILS WHILE REPLAYING INDEX RECORDS DUE TO LACK OF OBJECT TABLE SPACE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Rollforward fails while replaying index records due to lack of object table space The following forward recovery scenario may result in a system outage during rollforward: 1. Create backup1 2. Create first index I1 on a table 3. Create backup2 4. Restore backup1 and rollforward 5. Drop index I1 6. Restore backup2 and rollforward User will observe instance crash and one of the following messages might be logged in db2diag.log: sqldRedoUpsert: "Free space doesn't not match during redo" or loadOrValSubDMSDesc, "Failed fetching record from object table!" | |
Problem-Zusammenfassung: | |
The problem is that a change of index life LSN was not logged even though the life LSN did change when the index was mark bad. When the last "rollforward db <dbname> to end of logs" is executed, rollforward does NOT replay the drop index log record because the index life LSN in this log record is lesser than the current index life LSN from the object table entry. The record was not deleted from the object table; therefore, the space was not freed up. Then an error is enountered while redoing an insert there is not enough space in the object table page. | |
Local-Fix: | |
n/a | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Lösung | |
This APAR fix is targeted for Fix Pack 9. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IZ67734 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 06.01.2010 07.01.2010 07.01.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.0. | |
Problem behoben lt. FixList in der Version | |
9.7.0.2 |