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

MEMORY LEAK IN THE APPLICATION HEAP IF DATABASE USE UCACCC_400R1 OR
UCACCC_500R1 COLLATION AND STATEMENT USE "LIKE" PREDICATES

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
In a database with UCACCC_400R1 or UCACCC_500R1 collation the 
use of LIKE predicates results in a memory leak in the 
application heap. 
 
As a result of the leak, clean-up at the end of execution of a 
statement with a large filter will take a long time and may be 
observed when using the CLP as a long delay between the last 
result being displayed and a return to the shell prompt. 
 
The amount of memory leaked (and therefore the observable delay) 
is dependent on the number of rows evaluated by the LIKE 
statement. 
 
All leaked memory is released when the application heap is freed 
on session termination.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 10.5 Fix Pack 5                           * 
****************************************************************
Local Fix:
Solution
Problem Fixed In version 10.5 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.06.2014
13.03.2015
13.03.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList