home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC69309 Status: Closed

TYPE 4 JDBC APPLICATIONS CONNECTING TO A DB2 ON Z/OS SYSPLEX OR DB2
PURESCALE SERVER MIGHT HANG AFTER A NOROUTETOHOSTEXCEPTION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When using the IBM Data Server Driver for SQLJ and JDBC (also 
known as the JCC driver) in an application server 
connecting to a DB2 on z/OS Sysplex or DB2 pureScale server, 
applications might hang if they get a 
java.net.NoRouteToHostException. 
 
The hang only happens when using Type 4 connectivity 
with the JCC property enableSysplexWLB=true .
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of JDBC applications which use the the IBM Data Server * 
* Driver for SQLJ and JDBC (also                               * 
* known as the JCC driver) in an application server connecting * 
* to a DB2 on z/OS Sysplex or DB2 pureScale server.            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When using the IBM Data Server Driver for SQLJ and JDBC      * 
* (also known as the JCC driver) in an application server      * 
* connecting to a DB2 on z/OS Sysplex or DB2 pureScale server, * 
* applications might hang if they get a                        * 
* java.net.NoRouteToHostException.                             * 
*                                                              * 
* The hang only happens when using Type 4 connectivity with    * 
* the JCC property enableSysplexWLB=true                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************
Local Fix:
available fix packs:
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 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
Problem was first fixed in Version 9.7 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.06.2010
11.10.2010
11.10.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList