DB2 - Problem description
Problem IT11627 | Status: Closed |
PRIVATE MEMORY LEAK DUE TO AUDIT FOR EXECUTE CATEGORY. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * 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. | |
Solution | |
This problem was first fixed in DB2 V10.5 FixPack 7. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.10.2015 19.01.2016 19.01.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.7 |