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 IC83083 Status: Geschlossen

EXCESSIVE MON_HEAP MEMORY USAGE OR HANGS DUE TO LOST LOCKING OR ACTIVITIES
EVENT MONITOR RECORDS

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The LOCKING and ACTIVITIES event monitors make use of "fast 
writer records" to send event data from clients to the event 
monitor.   It is possible that in the course of generating 
deadlock, lock timeout, lockwait or activity events records may 
be inadvertently leaked so that they are unavailable for future 
reuse.  This can result in an increase consumption of MON_HEAP 
over time and can lead to a hang if all the fast writer records 
are leaked and MON_HEAP is exhausted. 
 
One possible symptom of this is that the Queue Manager 
Information displayed in the "db2pd -gfw" output may show zero 
free records available and have agents blocked waiting records 
to be made available.  For example: 
 
  Queue Manager Info 
    Current Number of Records: 1585 
    Free Records Available   : 0 
    Maximum Number of Records: 85000 
    Maximum Cached Records   : 30000 
    Minimum Cached Records   : 1000 
    Number of Agents Blocked : 1
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Anybody using LOCKING or ACTIVITIES event monitors.          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 Fix Pack 6                            * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 9.7 Fix Pack 6
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
02.05.2012
02.05.2012
02.05.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList