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

PRIVATE MEMORY LEAK DUE TO AUDIT FOR EXECUTE CATEGORY.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
The private memory for db2sysc process keeps growing if audit 
facility is enabled for EXECUTE or CONTEXT category. 
The db2pd command shows the following memory allocations consume 
large amount of private memory. 
 
$ db2pd -memblock pid=<db2sysc_pid> sort 
Memory blocks sorted by size: 
PoolID     PoolName   TotalSize(Bytes)     TotalCount LOC   File 
0                     217391816            961525     1428 
133962229 
0                     133844419            195608     1065 
133962229 
 
note: LOC (1428 and/or 1065) can slightly vary depending on the 
platform and 
versions. 
 
This leak issue is only applicable to DB2 V10.5 FP6, V10.1 FP5 
and V9.7 FP11.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use audit facility with EXECUTE or CONTEXT         * 
* category.                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V10.5 FixPack 7 or later.              * 
****************************************************************
Local-Fix:
Please turn off database audit which captures EXECUTE and 
CONTEXT events.
Lösung
This problem was first fixed in DB2 V10.5 FixPack 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
07.10.2015
19.01.2016
19.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList