|
Problem IC65507
|
Status: Closed |
PERFORMANCE ISSUE AND MEMORY LEAK WHEN USING TRANSACTION-LEVEL WORKLOAD BALANCING (WLB) |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
There are 2 problems that apply to non-java DB2 clients
accessing either a DB2 for z/OS (all supported versions) server
or a DB2 for LUW pureScale server (version 9.8 or later).
Problem 1 is that during transaction-level worklaod balancing
(WLB), if a member is dropped from the server list and is later
reinstated, it might continue to be ignored by the client for
WLB purposes.
Problem 2 is that with transaction-level WLB involving automatic
client reroute (ACR) retries, the client might use up more
memory than it should, resulting in the following error being
issued:
SQL1509N The statement cannot be processed because all
available
transports are in use, and no more transports can
be created.
Reason code: "1". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* There are 2 problems that apply to non-java DB2 clients *
* *
* accessing either a DB2 for z/OS (all supported versions) *
* server *
* or a DB2 for LUW pureScale server (version 9.8 or later). *
* *
* *
* *
* Problem 1 is that during transaction-level worklaod *
* balancing *
* (WLB), if a member is dropped from the server list and is *
* later *
* reinstated, it might continue to be ignored by the client *
* for *
* WLB purposes. *
* *
* *
* *
* Problem 2 is that with transaction-level WLB involving *
* automatic *
* client reroute (ACR) retries, the client might use up more *
* *
* memory than it should, resulting in the following error *
* being *
* issued: *
* *
* *
* *
* SQL1509N The statement cannot be processed because all *
* *
* available *
* *
* transports are in use, and no more transports *
* can *
* be created. *
* *
* *
* *
* Reason code: "1". *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7 Fix Pack 2. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 2. At a
minimum, this fix should be applied on the client. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.01.2010
13.05.2010
13.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
