DB2 FOR LUW / DB2FORLUW / A10 - DB2

Applications that are already connected while a compiler 
registry variable is updated dynamically may see the update only 
for the first subsequent statement and loose the update 
afterwards. These application needs to disconnect and reconnect 
for the update to take effect permanently. A database or 
instance restart is not required. 
 
The documented variables affected by this APAR are : 
 
   DB2_RESOLVE_CALL_CONFLICT 
   DB2_SELECTIVITY 
   DB2_SELUDI_COMM_BUFFER

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users making use of compiler registry variables              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4 or 10.5 Fix Pack 4    * 
****************************************************************

Applications that are already holding a connection while an 
affected variable is updated dynamically will permanently see 
the update only once they disconnect and reconnect. This issue 
can also be resolved by installing DB2 LUW 10.1 Fix Pack 4 or 
10.5 Fix Pack 4.

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 10.1 Fix Pack 4 or 10.5 Fix Pack 4

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC97635 
follow-up : 

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

11.11.2013
02.06.2014
02.06.2014