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

DOCUMENTATION OF CHANGES IN IBM DATA SERVER DRIVER FOR JDBC AND SQLJ
VERSION 3.61.75/4.11.77 FOR DB2 LUW V9.7 FIXPACK 3a

product:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problem description:
Documentation of changes in IBM Data Server Driver for JDBC 
and SQLJ version 3.61.75/4.11.77 for DB2 LUW V9.7 Fixpack 3a. 
The previous version was 3.61.65/4.11.69 for DB2 LUW V9.7 
Fixpack 3. 
 
____________________________________________________________ 
Type-2 z/OS: java.lang.NullPointerException will be thrown 
when pstmt.execute with input Clob retrieved from rs.getClob 
using Limited Block Fetch (LBF) and progressiveStreaming. 
(wsdbu00678588 wsdbu00678601) 
 
____________________________________________________________ 
Type-2 z/OS: Incorrect resultmetadata values may be obtained 
for stored procedure returned resultsets due to missing 
extended describe. (wsdbu00642448 wsdbu00677967) 
 
____________________________________________________________ 
All connectivity types: When the target server is v10 zOS, 
if using getObject to retrieve a XML data and then insert 
this data back to database, the driver will issue Exception 
-4225 with message: "The specified size of the InputStream, 
parameter #x, is less than the actual InputStream length." 
The problem has been fixed. 
(wsdbu00680437 wsdbu00680443) 
 
____________________________________________________________ 
Type 4 connectivity: When running aginst DB2 zOS v10 CM8, 
an SQL exception with error code -4499 may happen if the 
setBigDecimal method of PreparedStatement/CallableStatement 
is used under Java 5 and above. Now the problem is fixed. 
(wsdbu00683618) 
 
_________________________________________________________ 
Type-4 Connectivity: Under sysplexWLB environment, 
if set client statements and other set special 
register commands like set current schema are 
both set, an SQLException with SQLCODE204 (-204) 
might be thrown because these special registers 
might not set correctly by the JCC driver during 
the workload balancing. (wsdbu00674406) 
 
____________________________________________________________ 
Type-4 Connectivity: Under sysplexWLB environment, 
the workload was not balanced if the serverName 
property from the DataSource is set to a explicit 
IP address (e.g 9.30.111.111) instead of a 
hostname (e.g 'myHost') (wsdbu00677429) 
 
____________________________________________________________ 
SQLJ T4 Connectivity Type: An SQLException may occur 
in the SQLJ Bind process when running the SQLJ Binder 
with multiple ser files - either using a .grp file 
or placing them explicitly in thedb2sqljbind command. 
[jcc][sqlj][3056][11830]COMMENT ON PACKAGE FAILED. 
Error :  -107. 
If the comment String generated by the SQLJ Binder 
exceeds the length of the maximum allowable comment 
for the target server, the generated comment  will be 
modified to contain the name of the grp file (if used) 
or truncated to the maximum length. 
(wsdbu00682651) 
 
____________________________________________________________ 
SQLJ T4 Connectivity Type: An SQLException occurs 
in an  SQLJ  Program using Batched Inserts going through 
a  DB2 Connect  gateway to a target DB2 server on z/OS. 
This results in error -4428 or -4499 on the client. 
Additionally, it may cause the  DB2 server on z/OS to 
abend. This is now fixed in the JCC SQLJ Driver. This 
is a runtime fix only - there is no need to re-Customize or 
re-Bind the SQLJ Profile. 
(wsdbu00683600)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of the IBM Data Server Driver for JDBC and SQLJ        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW V9.7 Fixpack 3a                           * 
****************************************************************
Local Fix:
n/a
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
Problems fixed in DB2 LUW V9.7 Fixpack 3a
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.09.2010
25.05.2011
25.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
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.