|
Problem IC94485
|
Status: Closed |
FAILBACK TO PRIMARY DOES NOT OCCUR WHEN USING CLIENT AFFINITIES WITH AFFINITY FAILBACK INTERVAL |
| product: |
DB2 DATA SRVR D / DB2DSDRVR / A10 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* 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 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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
|
| Solution |
Upgrade to DB2 10.1 Fixpack 3 or above |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC94873 IC94874
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 31.07.2013
31.12.2014
31.12.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
