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

Crash in SQL PL associative arrays when allocating memory for new array
elements

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When using SQL PL associative arrays the DB2 instance may crash 
with a segmentation fault (signal #11 on Unix/Linux) or memory 
access violation (C0000005 on Windows) with the following stack: 
 
<redBlackTree::rbGetFirstNode> 
<associativeArrayHeader::getFirstNode> 
<associativeArrayHeader::getFirstIndex> 
<sqlriArrayDescriptor::destroyAllChildren> 
<sqlriArrayDescriptor::allocateDyn> 
<sqlriArrayDescriptor::setElement> 
<PVM::setArrayElement> 
<PVM::run> 
<pvm_entry> 
 <sqloInvokeFnArgs> 
<sqlriInvokerTrusted> 
<sqlriInvokeInvoker> 
<sqlricall> 
<sqlriSectInvoke> 
<sqlrr_process_execute_request> 
<sqlrr_execute> 
<sqljs_ddm_excsqlstt> 
<sqljsParse> 
<sqljsSqlam> 
<sqljsDriveRequests> 
<sqljsDrdaAsInnerDriver> 
<sqljsDrdaAsDriver> 
<sqeAgent::RunEDU> 
<sqlzRunEDU> 
<sqloInitEDUServices> 
 
This issue is caused by a logic problem during the error 
handling of a failure to allocate memory from the application 
heap for new elements in a SQL PL associative array. 
 
This APAR will fix the error handling to remove the crashing 
conditions such that the correct memory allocation failure 
message (such as SQL20442) will be returned.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See ERROR DESCRIPTION.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v9.7 Fixpack 6.                                   * 
****************************************************************
Local Fix:
available fix packs:
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
Problem first fixed in v9.7 Fixpack 6.  This fix should be 
applied to the DB2 server.
Workaround
See LOCAL FIX.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.12.2011
04.06.2012
04.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList