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 IC84330 Status: Closed

POSSIBLE MEMORY LEAK IN SQLNNLITERALREPLACE() WITH STATEMENT CONCENTRATOR
ON

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If the statement concentrator is ON some memory leak can occur 
in case the SQL statement cannot be processed properly by the 
concentrator. The size of the leak will be a bit bigger than the 
size of the statement itself. 
 
The leak can be detected using 'db2pd -memb' and will show up in 
file sqlnnLiteralReplace.C file. Monitor if the Totalsize of 
File 
No.2793471063(sqlnnLiteralReplace.C) & LOC 858 is increasing.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* None                                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* None                                                         * 
****************************************************************
Local Fix:
Set STMT_CONC to OFF
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
01.04.2013
01.04.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList