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 IT05614 Status: Closed

REMOVE MESSAGES SQLPUPDATEMEMSTATUS, PROBE:611 FROM DB2DIAG.LOG WHEN STMM
IS TUNING LOCKLIST

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The following message is unnecessary when STMM is tuning the 
locklist variable: 
 
xxxx-xx-xx-xx.xx.xx.xxxxx-xxxx XXXXXXXXXXX          LEVEL: 
Warning 
PID     : xxxxxxxx             TID : xxxxx          PROC : 
db2sysc 0 
INSTANCE: db2XXX               NODE : 000           DB   : XXX 
APPHDL  : 0-xxxxx              APPID: XXXX 
AUTHID  : xxxxxxx              HOSTNAME: xxxxxxxxxxx 
EDUID   : xxxxx                EDUNAME: db2agent (XXX) 0 
FUNCTION: DB2 UDB, lock manager, sqlpUpdateMemStatus, probe:611 
DATA #1 : <preformatted> 
Locking memory management: LLM-memory low. 
Escalation threshold activated. 
LLM-lock list size = 432076 
LLM-lock list available = 197
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users running DB2 10.5 up to Fix Pack 5                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fix Pack 6 or later                      * 
****************************************************************
Local Fix:
N/A
Solution
See Error Description
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.11.2014
15.07.2015
15.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 FixList