|
Problem IC75268
|
Status: Closed |
STMM DOES NOT TUNE SORTHEAP CORRECTLY FOR INDEX CREATION (INCLUDING LOAD,REORG) |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
Due to a logic error, STMM does not cost SORT operations for
index creation during the initial "insert" phase.
As a result, SORTHEAP may not be tuned appropriately.
This impacts longer index creations which may benefit from
higher SORTHEAP settings.
Activities impacted include LOAD, REORG, CREATE INDEX. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Systems configured with STMM tuning SORTHEAP *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.5 Fix Pack 8 OR configure SORTHEAP *
* (and SHEAPTHRES_SHR) to a fixed value *
**************************************************************** |
| Local Fix: |
Manually tune SORTHEAP, SHEAPTHRES_SHR to desired values if the
database is configured for AUTOMATIC Sort tuning.
It is possible to do this dynamically with a database
connection, and return to AUTOMATIC after the activity involving
index creation is complete. |
| 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 |
Problem first fixed in DB2 Version 9.5 Fix Pack 8 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC75331
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.03.2011
11.08.2011
11.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
