DB2 DATA SRVR D / DB2DSDRVR / A50 - DB2

With the driver shipped with DB2 10.1 and above, there are 
scenarios where client affinities failback may not succeed long 
after the Primary server is up. This occurs because the failback 
thread that routinely checks the status of the Primary Server 
continues to fail with an unhandled exception. 
 
If driver traces are captured, they show the affinity failback 
thread making attempts that end abruptly without any indication 
of the result. 
 
A normal failback attempt begins with the following trace entry: 
 
"===Affinity fail back timer waking up=== isPrimaryUp=false" 
 
and ends with the following trace entry: 
 
"===Primary server is still down===" 
     or 
"===Affinity fail back timer ping end: Primary server is up===" 
 
When this issue occurs multiple instances of begin entries will 
be seen that have no corresponding ending entry.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of IBM Data Server Driver for JDBC and SQLJ        * 
* shipped with DB2 10.5 releases earlier than DB2 10.5 Fixpack * 
* 4                                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Refer Error Description                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fixpack 4                                * 
****************************************************************

Upgrade to DB2 10.5 Fixpack 4

not known / see Local fix

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

02.06.2014
08.09.2014
08.09.2014