All connectivity types: Application using JCC driver
receives SQL exception with SQLCODE=-401 from DB2 server
when updating a column defined in DB2 as SMALLINT using
setBoolean() api of java.sql.PreparedStatement.
(RTC 24251)
------------------------------------------------------------
Type-2 LUW connectivity: When connection is to DB2 z/OS,
invoking java.sql.Statement setQueryTimeout() api results
in a SqlFeatureNotSupportedException (SQLCODE -4450). The
exception occurs irrespective of the
queryTimeoutInterruptProcessingMode value configured by the
user.(RTC 26821)
------------------------------------------------------------
All connectivities: Improvements in the JCC common code to
reduce CPU impact and enhance performance. (RTC 27371)
------------------------------------------------------------
Type-4 connectivity: The JCC driver returns incorrect
length, precision and scale metadata for TIMESTAMP and
TIMESTAMP WITH TIMEZONE parameters in a stored procedure.
The incorrect parameter metadata recorded in a pureQuery
capture file causes corresponding stored procedure
invocations in static mode to fail with SQLCODE -180.
(RTC 27458)
------------------------------------------------------------
Type-2 z/OS connectivity: Various minor improvements to
make loading the driver and connection establishment less
expensive in terms CPU and memory. (RTC 30648)
------------------------------------------------------------
Type-4 connectivity: When using client affinities with a
fail back interval, the driver does not fail back to the
primary server even though it may have become available.
(RTC 32630)
------------------------------------------------------------
Type-4 XA Connectivity: Driver does not close non-XA
transaction (with autocommit on) in case of an exception
in execution. After the exception, the transaction remains
open causing the next XA start to fail. (RTC 28121)
------------------------------------------------------------
Type-4 Connectivity: In a workload balancing environment,
Connection might acquire a specific transport object from the
pool that was previously used by other thread. In this
scenario, driver should do a heavy weight reset on that
transport once but not on subsequent reuse by the same
connection. Due to multiple reset flows the system
performance degrades. (RTC 22659)
------------------------------------------------------------
Type-2 Connectivity: Driver was flowing the
SET CURRENT PACKAGESET SQL statement at the end of the
getConnection processing. In some cases this caused a global
transaction to be started, leading to unpredictable results
including SQLCODE913(-913). This issue is fixed in
setCurrentPackageSet() and setDB2CurrentPackageSet().
(RTC 28602)
------------------------------------------------------------
Type-2 z/OS connectivity: SQLJ application encounters data
corruption in a multithreaded environment. This happens when
callableStatement is executed under WAS with statement
caching enabled. This issue is fixed.(RTC 30234)
------------------------------------------------------------
Type-4 Connectivity: IBM DB2 Driver for JDBC and SQLJ
parses two single quotes in a callable statement
incorrectly when the target server is DB2 for z/OS.
(RTC 26291)
------------------------------------------------------------
Type-4 XA Connectivity: In a workload balancing
and XA transaction environment, a SQLCODE4228(-4228) error
might return to the application if auto failover has
occurred during a local transaction. (RTC 23193)
------------------------------------------------------------
Type-4 connectivity: In case of TLS certificate
authentication, JCC should treat empty password as NULL.
(RTC 31111)
------------------------------------------------------------
Type-2 connectivity: If JCC Client and DB2 server are on
different operating system columns of numeric data types
(SMALLINT, INTEGER, etc) may get inserted into the database
with incorrect values. (RTC 28962)
------------------------------------------------------------
Type-4 connectivity: If a security mechanism value of 3 is
set on a datasource while a different value is provided via
the global db2.jcc.securityMechanism property, then the
datasource value is incorrectly overridden by the global
property. (RTC 21518)
------------------------------------------------------------
Type-4 Connectivity: Driver throws SQLCODE4474(-4474) while
setting CURRENTPACKAGEPATH for ZOS trusted connection
environment. (RTC 27990)
------------------------------------------------------------
T2ZOS/SQLJ connectivity: Application encounters the following
message: "Invalid parameter n: Parameter is not an OUT or INOUT
parameter.ERRORCODE=-4461, SQLSTATE=42815". This happens when
callableStatement is executed under WAS with statement
caching enabled. (RTC 27123 )
------------------------------------------------------------
Type-4 connectivity:A java.lang.ArrayIndexOutOfBoundsException:
Array index out of range: 255, may be thrown by the driver
when invoking a stored procedure that has array types as
parameters and number of parameters are more than 83.
The problem has been fixed. |
