DB2 - Problembeschreibung
Problem IC77969 | Status: Geschlossen |
UPGRADE TO DB2 9.7 CAN REQUIRE AN UNEXPECTEDLY LONG TIME FOR INDEX REBUILD | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problembeschreibung: | |
In DB2 9.7 new meta data has been added to all index root pages. During database upgrade we check if there is enough space to upgrade the root page page and if there is not, then we mark the entire index object as invalid and the index will be rebuilt after database upgrade. Index rebuild can take several hours on large tables and will acquire and hold a Z lock on the table for the entire duration of the index rebuild. This can leave the database unusable for several hours after the upgrade. This change prevents the index manager from filling up an index root page beyond the point where there would not be enough space to upgrade it to 9.7 or later. | |
Problem-Zusammenfassung: | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Kommentar | |
The preventative code is available in DB2 9.1.0.11 and a workaround will also be delivered to DB2 9.7.0.6 to more gracefully handle this scenario | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC78041 IC78042 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 05.08.2011 08.12.2011 08.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
9.1.0.11 |