DB2 - Problem description
Problem IC93301 | Status: Closed |
SORTS FROM SMALL INDEX BUILDS OVER-RESERVE SORT MEMORY, STMM MAY UNNECESSARILY INCREASE SORT TUNING | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Index builds, including during reorg, reserve the full sortheap from sort memory. Most index builds are done in parallel with 6 subagents, so most reserve 6 full sortheaps. Much of this memory may never be allocated for smaller index builds. Since STMM tuning is based on the sort reservation, STMM may react by increasing the sort configuration, which may cause a subsequent index build to reserve even more memory. Generally there is no adverse symptom from this other than an STMM-tuned configuration may seem to set SHEAPTHRES_SHR and SORTHEAP unnecessarily high. In extreme cases other STMM consumers may be decreased, causing some performance degradation. One method of determining this issue exists is by examining a database snapshot. The high water mark for reserved shared sort usage: Shared Sort heap high water mark = 70129 ( 4K pages ) May be much higher than the actual shared sort pool usage : Memory Pool Type = Shared Sort Heap Current size (bytes) = 0 High water mark (bytes) = 20512768 Configured size (bytes) = 307200000 In this case, the highest reserved sort memory was 280 Mb (70129 4K pages), but the actual allocated memory only reached 20MB (20512768 bytes). | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 4 * **************************************************************** | |
Local Fix: | |
configure sortheap, sheapthres_shr to fixed values | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 Version 10.1 Fix Pack 4 | |
Workaround | |
See Local Fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.06.2013 02.06.2014 10.06.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 | |
10.1.0.4 |