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

CRASH DURING LIKE PROCESSING WITH LONG PREDICATES AND MEMORY DEBUG OPTIONS
TURNED ON

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In V97 fixpack 4 only, if a query contains a "like" predicate 
where the column is a "long" type 
such as long varchar, then there is a small timing window that 
might cause a memory corruption 
when a section is being freed during the sql workspace memory 
management logic. 
 
Since this timing window is small, the actual symptom of the 
corruption has never 
been seen to date, but the exposure has been identified and 
fixed with this APAR. 
 
Because this is a memory corruption, there may be a few 
different possible symptoms, and 
an instance crash is possible. However, the problem itself was 
only discovered when certain 
memory debug options were enabled, which changed the timing and 
memory conditions that 
enabled the discovery of the problem. 
 
In that case, a crash was detected with the following stack: 
 
sqlri_like_free 
sqlricls_complex 
sqlricls 
sqlriecc 
sqlriCloseExecuteSectionComplex 
sqlriCloseExecuteSection 
sqlrr_process_execute_request 
sqlrr_execute 
sqljs_ddm_excsqlstt 
sqljsParseRdbAccessed 
sqljsParse
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* 97FP4 users using LIKE processing with LONG predicates and   * 
* memory debug options turned on.                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Crash during LIKE processing with LONG predicates and memory * 
* debug options turned on.                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V97FP5 containing the fix.                        * 
****************************************************************
Local Fix:
available fix packs:
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Fixed in 97FP5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.08.2011
19.01.2012
19.01.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList