|
Problem IC70125
|
Status: Closed |
CONNECTION LEVEL LOAD BALANCING OCCURS EVEN WHEN ENABLEWLB IS NOT SET |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
LUW client automatically enables Connection level load balancing
by default if connection is made directly to DB2 for zOS even
when transaction level load balancing (enableWLB) is not
enabled.
The initial ( very first) connection uses the the connectivity
information to route the connection to DB2 for zOS sever. The
subsequent new connections are distributed and routed based on
the sysplex information returned as server list by the
server.The connections are distributed by client instead of
sysplex distributor DVIPA. This also prevents single member
access on DB2 for zOS. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 Connect *
****************************************************************
* PROBLEM DESCRIPTION: *
* LUW client automatically enables Connection level load *
* balancing *
* by default if connection is made directly to DB2 for zOS *
* even *
* when transaction level load balancing (enableWLB) is not *
* *
* enabled. *
* *
* *
* *
* The initial ( very first) connection uses the the *
* connectivity *
* information to route the connection to DB2 for zOS sever. *
* The *
* subsequent new connections are distributed and routed based *
* on *
* the sysplex information returned as server list by the *
* *
* server.The connections are distributed by client instead of *
* *
* sysplex distributor DVIPA. This also prevents single member *
* *
* access on DB2 for zOS. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Connect V97.fp3a. *
**************************************************************** |
| Local Fix: |
Connection-level WLB can be explicitly disabled by setting
either of the following :
1. By setting "ConnectionLevelLoadBalancing=false" in
db2dsdriver.cfg.
2. Catalog a DCS directory without specifying SYSPLEX as a DCS
parameter.
3. Set DISABLESYSPLEX=TRUE in db2cli.ini file
4. Set connection attribute SQL_ATTR_DISABLE_SYSPLEX=1 |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First Fixed in DB2 Version 9.7 Fix Pack 3a |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.07.2010
28.10.2010
11.07.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3,
9.7.FP3A
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
