DB2 DATA SRVR D / DB2DSDRVR / A10 - DB2

IBM Data Server Driver for JDBC and SQLJ configured to use 
client affinities with an affinityFailbackInterval does not fail 
back to the primary even after it becomes available. 
 
The driver initially connects to the primary, and fails over to 
one of the secondary servers in the client affinities list if 
the primary goes down. This is expected. However, now the driver 
is expected to verify the primary server status once every 
'affinityFailbackInterval'. If the primary is found to be 
available again, the driver needs to failback to it at the first 
opportunity it can. Due to the present issue, the driver's 
verification of the primary server status terminates abnormally 
resulting in the  driver continuing to operate with the 
secondary server without ever failing back to the primary. 
 
One symptom of this issue is that the driver traces continue to 
show 'isPrimaryUp=false' long after the primary has become 
available.

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

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

Upgrade to DB2 10.1 Fixpack 3 or above

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC94873 IC94874 
Nachfolger : 

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

31.07.2013
31.12.2014
31.12.2014