home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC97664 Status: Closed

PRIVATE MEMORY LEAK IN DB2SYSC TRIGGERED BY EXECUTING XML QUERIES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Executing XML queries may cause DB2 to leak private memory on 
the following levels : 
9.7 Fix Pack 8 and higher 
10.1 Fix Pack 3 and higher 
10.5 GA and higher 
 
This memory is not tracked by any DB2 memory monitoring 
utilities and can only be seen at an aggregate level by OS 
monitoring tools.  If a system experiences excessive memory 
usage and associated symptoms (detuning by STMM) after upgrading 
to the above levels and is using XML, this APAR is a likely 
candidate.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Servers processing XML Data                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 Version 10.1 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.11.2013
11.06.2014
11.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList