Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC77969 Status: Closed

UPGRADE TO DB2 9.7 CAN REQUIRE AN UNEXPECTEDLY LONG TIME FOR INDEX REBUILD

product:
DB2 FOR LUW / DB2FORLUW / 910 - 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 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 Summary:
Local Fix:
available fix packs:
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
Workaround
not known / see Local fix
Comment
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-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC78041 IC78042 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.08.2011
08.12.2011
08.12.2011
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.11 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.