|
Problem IC84135
|
Status: Closed |
STMM TUNES SHARED SORT MEMORY TOO HIGH |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Problem Description:
=============
STMM may tune shared sort memory too high when throttling has
occured as part of trying to satisfy STMM's "Minimum Size"
calculation.
The best way to be sure of this symptom is when the "Minimum
Size" for Shared Sort Heap in the STMM log is more than 1.25
times the current or peak shared sort memory usage (seen in a
database snapshot).
For example, below the Minimum Size is 5288250, but the database
snapshot shows a high water mark of only 3882760. The Minimum
Size is more than 1.25 x the high water mark, which is too high,
and likely caused by this APAR.
*** stmmCostBenefitRecord ***
Type: SHEAPTHRES_SHR
PageSize: 4096
...
Current Size: 4363267 (this is the current configured size)
Minimum Size: 5288250
Database Snapshot:
Total Shared Sort heap allocated = 3138402
Shared Sort heap high water mark = 3882760 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Systems configured to have STMM tune Sort memory *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 1 *
**************************************************************** |
| Local Fix: |
Use a fixed size for SHEAPTHRES_SHR |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 1 |
| Workaround |
See Local Fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.06.2012
02.11.2012
02.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
