DB2 - Problem description
Problem IT05028 | Status: Closed |
RESTART DATABASE TAKES LONGER THAN NECESSARY ON SYSTEMS WITH A LARGE NUMBER OF TABLES | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
When INDEXREC is set to RESTART, the RESTART DATABASE command will rebuild any indexes marked as needing to be rebuilt. All table objects in the database must be checked to determine the state of their indexes. This process may take longer than necessary as all metadata is loaded, requiring reads from disk. Systems making use of table partitioning are more heavily impacted as each table partition is a separate object. Compressed tables are also more expensive due to the cost of loading the compression dictionary (and each table partition has its own dictionary). This APAR fix substantially reduces the amount of metadata which must be loaded when checking the state of a table's indexes. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 systems with a large number of tables are affected * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 5 * **************************************************************** | |
Local Fix: | |
Solution | |
Problem first fixed in DB2 Version 10.1 Fix Pack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.10.2014 21.07.2015 21.07.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.5 |