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 IC65389 Status: Closed

DOCUMENTATION OF CHANGES IN IBM DATA SERVER DRIVER FOR JDBC AND SQLJ
VERSION 3.8.70 FOR DB2 LUW V9 FIXPACK 9

product:
DB2 CONNECT / DB2CONNCT / 910 - DB2
Problem description:
============================================================ 
Documentation of changes in IBM Data Server Driver for JDBC 
and SQLJ version 3.8.70 for DB2 LUW V9 Fixpack 9. 
The previous version was 3.8.62 for DB2 LUW V9 Fixpack 8. 
 
____________________________________________________________ 
Type-4 Connectivity: A NullPointerException occurs 
when connectionConcentrator property is set to true and 
sysplexWLB property is set to false and the JCC trace is 
enabled. (131088) 
 
____________________________________________________________ 
Type-4 Connectivity: Automatic client reroute (ACR) to 
other members of a datasharing group may not occur when 
Sysplex workload balancing (WLB) is enabled, resulting in 
SQLCODE4499 (-4499) when one member goes down. (133488) 
 
____________________________________________________________ 
All Connectivity types: If a SQLWarning occurs 
with the following message: 
  [ibm][db2][jcc][10223][10837] Input data type mismatch, 
  see chained exceptions; will retry execution using 
  describe input information. 
  Please change application to use an input data type that 
  matches the database column type as required by JDBC 
  semantics. 
The subsequent SQLWarning.getNextWarning() will result in 
a SQLException with the following message: 
"SQLWarning chain holds value that is not a SQLWarning" 
instead of an SQLWarning. (136535) 
 
____________________________________________________________ 
Type-4 Connectivity:  Under a Sysplex workload-balancing 
(WLB) environment, the CLIENT_APPLNAME special register 
might be missing after transaction boundary (commit, 
rollback and etc) if the CLIENT_APPLNAME special register 
was originally set at the data source level by the 
following api call: 
dataSource.setClientApplicationInformation(). (132276) 
 
____________________________________________________________ 
All Connectivities: A "java.lang.ClassCastException" 
exception is encountered when 
PreparedStatement.executeBatch () is called against 
DB2 for z/OS to execute an INSERT FROM SELECT statement. 
(130216) 
 
____________________________________________________________ 
Type-4 Connectivity: SQLCODE99999 (-99999) with message 
"String exceeded maximum length of 32767" is encountered 
if invoking a stored procedure on DB2 for z/OS and 
using the setString() method where string length exceeds 
32767.  The problem has been corrected. 
(134607) 
 
____________________________________________________________ 
T4 Connectivity: When the driver performs client reroute 
from a DB2 server with a low level security manager to a 
server with a high security manager, the driver throws a 
SQLException with SQLCODE4499 (-4499).  (137441) 
 
____________________________________________________________ 
All Connectivities: When Blobs and Clobs are used as input 
parameters in a stored procedure call with the sendDataAsIs 
property set to default (false) against DB2 for z/OS, an 
illegal conversion exception is thrown.  (137803)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of the IBM Data Server Driver for JDBC and SQLJ        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.1 Fixpack 9                                    * 
****************************************************************
Local Fix:
n/a
available fix packs:
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
Problems fixed in DB2 LUW V9.1 Fixpack 9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.01.2010
07.04.2010
07.04.2010
Problem solved at the following versions (IBM BugInfos)
9.1.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.9 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.