home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT02789 Status: Geschlossen

LOCK ESCALATIONS WITH REASON CODE: "2" MIGHT BE REPORTED WHEN
LOCKLIST MEMORY WAS NOT EXCEEDED

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Under rare circumstances you might occasionally observe lock 
escalations with Reason code: "2" reported in db2diag.log: 
 
2014-05-21-10.32.34.339539+120 E5629642A881         LEVEL: 
Warning 
PID     : 11665914             TID : 47774          PROC : 
db2sysc 13 
INSTANCE: db2inst1             NODE : 013           DB   : DWH 
 
APPHDL  : 0-35424              APPID: 1.1.1.1.62647.140521083127 
 
AUTHID  : db2inst1             HOSTNAME: myhost 
 
EDUID   : 47774                EDUNAME: db2agntp (DWH_SV) 13 
 
FUNCTION: DB2 UDB, data management, sqldEscalateLocks, probe:2 
 
MESSAGE : ADM5500W  The database manager is performing lock 
escalation. 
The affected application is named "db2bp", and is associated 
with 
the workload name "SYSDEFAULTUSERWORKLOAD" and application ID 
 
"1.1.1.1.62647.140521083127" at member "13". The total 
 
number of locks currently held is "445958", and the target 
number of 
locks to hold is "222979".  Reason code: "2" 
 
Reason Code "2" would mean that LOCKLIST memory is exceeded. 
However, under rare circumstances this reporting might be wrong 
and misleading while the real cause for the lock escalation was 
triggered by MAXLOCKS and a Reason Code "1" should have been 
reported instead.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************
Local-Fix:
Lösung
First fixed in DB2 Version 10.1 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.06.2014
15.07.2015
15.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList