home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC65507 Status: Geschlossen

PERFORMANCE ISSUE AND MEMORY LEAK WHEN USING TRANSACTION-LEVEL WORKLOAD
BALANCING (WLB)

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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:
verfügbare FixPacks:
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

Lösung
Problem was first fixed in Version 9.7 Fix Pack 2.  At a 
minimum, this fix should be applied on the client.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.01.2010
13.05.2010
13.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList