DB2 FOR LUW / DB2FORLUW / A10 - DB2

This is a concurrent access issue when one thread is traversing 
the environment's list of database connections looking for a 
database connection handle and another is freeing a database 
connection handle on the list and the memory happens to be 
returned to the OS. 
 
The stack of the crash may looks as follows: 
 
db2app64!CLI_sqlDisconnect 
db2app64!SQLDisconnect2 
db2app64!SQLDisconnect 
... 
 
This APAR adds latching code when traversing the list of 
database connection handles.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V10.1 users                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fix Pack 5 or higher.                   * 
****************************************************************

This crash condition can be minimized by reducing the number of 
database connection handles per environment handle.

First fixed in DB2 V10.1 Fix Pack 5

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

07.07.2014
31.07.2015
31.07.2015