suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT38241 Status: Closed

ALTERNATE SERVER BECOMES PRIMARY SERVER WHEN BOTH PRIMARY AND ALTERNATE
SERVERS ARE DOWN DURING DB2 JCC ACR

product:
DB2 CONNECT / DB2CONNCT / B50 - DB2
Problem description:
When both primary and alternate servers are down initially
before first connection is established with enableSysplexWLB =
true,driver does not retry with primary server after first
trial.
The driver Continues to retry with alternate server based on
'maxRetriesForClientReroute' property if set, and if not set,
retries with alternate server default number of times, however,
the driver retries in both these cases only to alternate server
i.e alternate server becomes both the primary and alternate
server and original primary server is never retried for
connectivity.
The example scenario is this:
Primary server A
alternate server B
maxRetriesForClientReroute = 3
Both A and B are down.
Connection is attempted to A and fails with -4499
JCC driver retries as follows:
retry 1: Primary server A
alternate server B
retry 2: primary server B
alternate server B
retry 3: primary server B
alternate server B
The expected behavior is:
retry 1: Primary server A
alternate server B
retry 2: Primary server A
alternate server B
retry 3: Primary server A
alternate server B
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Db2 Connect users                                            *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to JCC driver on Db2 version V11.5.7.0               *
****************************************************************
Local Fix:
NA
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Db2 Connect users                                            *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to JCC driver on Db2 version V11.5.7.0               *
****************************************************************
Comment
Fixed in Db2 V11.5.7.0
If first connection is not established and enableSysplexWLB =
true, restore the primary server details after retrying with
alternate server list if available.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.09.2021
30.11.2021
24.10.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)