|
Problem IC73478
|
Status: Closed |
UPGRADE TO DB2 9.7 CAN REQUIRE AN UNEXPECTEDLY LONG TIME FOR INDEX REBUILD |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
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
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 adds a new service option to the db2dart tool in 9.5
so that a customer may determine which indexes will need to be
rebuilt after database upgrade to DB2 9.7. The new code will
execute when db2dart is run with both the "/ico y" and "/serv
16" options.
Usage: db2dart <dbName> /ico y /serv 16 /scr m
The "/ico y /serv 16" can also be used with actions /DB (the
default) or /T or /TS. |
| Problem Summary: |
|
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Comment |
The new db2dart option has been added to DB2 9.5.0.8. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.12.2010
07.07.2011
04.04.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
