DB2 FOR LUW / DB2FORLUW / A50 - DB2

Memory overwrite can happen when arrays with elements of large 
size are used (example: create type arrayCLOB as clob(2M) 
array[]) and  assignments to the same element in array either 
fluctuate greatly: 
 
set size large 
set size tiny 
set size large 
set size tiny 
etc.. 
 
or go up: 
 
set size large 
set size larger 
set size even larger 
set size even larger then before 
etc.. 
 
This can occur when calling MONREPORT.CURRENTSQL routine. 
 
The stack trace can be vary since this is memory corruption 
problem. Here is an example: 
 
pdLog 
diagnoseMemoryCorruptionAndCrash 
MemTreePreallocateAndInsert 
allocateMemoryBlock 
sqlogmblkEx 
allocateDyn 
setElement 
appendElement 
sqlriArrayAgg 
sqlriagg 
sqlriSectInvoke 
sqlrr_process_execute_request 
sqlrr_execute 
run 
pvm_entry 
sqloInvoke 
sqlriInvokerTrusted 
sqlriInvokeInvoke 
sqlricall 
 ...

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 1.                      * 
****************************************************************

Not using array data types.

DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

First fixed in Version 10.5 Fix Pack 1.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

27.08.2013
04.11.2013
04.11.2013