home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IT05485 Status: Closed

STMM LOCKLIST TUNING DECREASES FAIL REPETITIVELY ATTEMPTING TO REDUCE
LOCKLIST SIZE MORE THAN WHAT CAN BE FREED

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The STMM tuner may log frequent messages to the STMM log files 
about failing to decrease the Locklist.  This is because the 
calculation is based on locklist "in use", with the assumption 
that remaining locklist "not in use" can be freed.  However, 
some of the "not in use" locklist may be spread around on 
partially-used larger units of memory managed within the 
locklist, and those areas cannot be freed.  The STMM tuner needs 
to determine how many larger units of memory are completely free 
in order to correctly determine the maximum possible reduction 
in locklist size. 
 
STMM log messages about locklist decrease tuning failures appear 
similar to : 
 
EDUID   : 99999               EDUNAME: db2stmm (SAMPLE) 0 
FUNCTION: DB2 UDB, Self tuning memory manager, 
stmmUpdateDBConfig, probe:290 
MESSAGE : ZRC=0x82AE00A6=-2102525786=STMM_DYNAMIC_UPDATE_FAILED 
          "STMM dynamic update failed" 
DATA #1 : String, 78 bytes 
Dynamic update failed for parameter Locklist. Attempted update 
value is 100000 
 
Note that isolated appearances of these messsages may still be 
normal due to timing.  Even when repetitive messages occur, the 
impact on STMM tuning overall is minimal.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Systems using STMM to tune LOCKLIST                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Problem is cosmetic and can be ignored                       * 
****************************************************************
Local Fix:


Solution


Problem first fixed in DB2 Version 9.7 Fix Pack 11


Workaround


not known / see Local fix


Timestamps


Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

10.11.2014
23.10.2015
23.10.2015


Problem solved at the following versions (IBM BugInfos)


9.7.FP11



Problem solved according to the fixlist(s) of the following version(s)


9.7.0.11

FixList