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

MEMORY LEAK IS POSSIBLE IF CULTURALLY CORRECT DATABASE IS USED AND QUERY
HAS LIKE PREDICATE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Memory leak can occur if a culturally correct database is used, 
and a query has like predicate. 
 
For example: 
CREATE DATABASE  UTF8 COLLATE  USING UCA500R1_LEN_S2 
 
Running queries against character columns using LIKE predicate 
can result in a memory leak. 
The problem does not happen in DPF databases. 
The problem does not happen if dbm cfg parameter INTRA_PARALLEL 
is set to YES.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* V9.7 users                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Memory leak can occur if a culturally correct database is    * 
* used,                                                        * 
* and a query has like predicate.                              * 
*                                                              * 
*                                                              * 
*                                                              * 
* For example:                                                 * 
*                                                              * 
* CREATE DATABASE  UTF8 COLLATE  USING UCA500R1_LEN_S2         * 
*                                                              * 
*                                                              * 
*                                                              * 
* Running queries against character columns using LIKE         * 
* predicate                                                    * 
* can result in a memory leak.                                 * 
*                                                              * 
* The problem does not happen in DPF databases.                * 
*                                                              * 
* The problem does not happen if dbm cfg parameter             * 
* INTRA_PARALLEL                                               * 
* is set to YES.                                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to fix pack 3                                        * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC69280 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.06.2010
23.09.2010
23.09.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList