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

FILE EVENT MONITOR LEAKS PRIVATE MEMORY WHEN FAILING TO WRITE OUT EVENT
HEADER

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
A file event monitor may leak private memory when it fails to 
write out the header of a monitored event.  This may occur if 
the defined MAXFILESIZE / MAXFILES limit is reached or if 
filesystem space is exhausted. 
 
In the case of a deadlock event, if there is a large number of 
locks involved, the leaked memory may be large and cause memory 
usage problems on a system (eg. paging). 
 
A db2diag.log message is associated with the leak : 
EDUID   : 94323                EDUNAME: db2evmli (DEADLOCK_MON) 
0 
FUNCTION: DB2 UDB, database monitor, sqmEvmonBuffer::write_data, 
probe:10 
MESSAGE : ZRC=0x800D002B=-2146631637=SQLM_RC_EVFULL "monitor 
full of data" 
          DIA8052C The Event Monitor "" has reached its file 
capacity. Delete 
          the files in the target directory "" or move them to 
another 
          directory. 
 
The memory growth occurs in the PERSISTENT_PRIVATE memory pool 
and can be monitored using the MON_GET_MEMORY_POOL monitor 
routine. 
 
db2pd -memblocks <db2sysc PID> 
may show a growing amount of memory allocations from a file ID 
of 3401466018: 
PoolID     PoolName   TotalSize(Bytes)     TotalCount LOC   File 
0                     2272875936           1          4437 
3401466018 
0                     2272869259           1          4437 
3401466018 
...
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All systems                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Address limitations triggering the leak (see local fix)      * 
****************************************************************
Local-Fix:
Increase the MAXFILESIZE, MAXFILES attributes for the file event 
monitor and/or increase the filesystem space available to the 
event monitor
verfügbare FixPacks:
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

Lösung
Problem first fixed in DB2 Version 10.1 Fix Pack 3
Workaround
see Local Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.12.2012
04.12.2013
04.12.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList