DB2 FOR LUW / DB2FORLUW / A50 - DB2

When there is a mixture of CLI statements being executed on one 
connection, if one statement retrieves LOB data whilst another 
statement is still retrieving a result set via SQLFetch, then 
there is a possibility that a stale pointer will write data into 
a cached DB2 server side cursor buffer. 
This can lead to a crash in function csmGetNewCDBBuffer as the 
code reuses the buffer. 
 
As a secondary symptom, it can also lead to a wrong 
interpretation of data leading to unexpected symptoms during the 
SQLFetch e.g. error -30020 , or a "data truncation warning" or 
different as the code will not have written data to the right 
location and whatever data happens to be in memory will be read 
instead.

**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix    * 
* Pack 4) or Later                                             * 
****************************************************************

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 DB2 Cancun Release 10.5.0.4 (also known as Fix 
Pack 4)

not known / see Local fix

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

11.06.2014
13.10.2014
13.10.2014