Type-4 connectivity: SQLException with ERRORCODE=-4228
maybe received by an application when using a connection
with enableSysplexWLB=true and executing a
preparedStatement containing parameters of the type BLOB,
CLOB, LONGVARCHAR, LONGVARBINARY, BINARY, VARGRAPHIC or
LONGVARGRAPHIC.
(RTC 39666)
Type-4 connectivity: The Connection's isValid(int timeout)
API may throw NPE when client reroute is enabled. Also,
the isValid (int timeout) API may not honor the specified
timeout in certain scenarios.
(RTC 35828)
Type-4 connectivity: When an XADataSource with
enableSysplexWLB property configured as true is used, a
gradual growth in total transport object count occurs.
Over time, the total transport object count may reach the
maximum allowed causing all subsequent operations to fail
with the SQLException Timeout getting a transport object from
pool. ERRORCODE=-4210, SQLSTATE=57033. (RTC 35561)
Type-4 Connectivity: The JCC Driver will not hold
transport until the end of new unit of work. A possible
symptom is occurrence of SQLException with SQLCODE=-811
which goes away on turning off transport pooling.
(RTC 45936)
Type-4 connectivity: The getCatalog() API always returns
CURRENT SERVER value by default which is incorrect. A new
global property "retCatalogAsServer" added to control the
RETCAT option for getCatalog() API used when invoking the
SYSIBM.SQLTABLES stored procedure. ( RTC 44231)
Type-4 connectivity: Serviceability feature to auto dump
information related to selected SQLCODES such as -1224,
-204, -30108, -4499, -20542, -4210 in a data-sharing
environment. The auto dump information includes general
information like last DRDA exchanged, stack trace of the
exception, error code/SQLCA, DataSource properties along
with any other information relevant to the specific
SQLCODE. (RTC 39840)
Type-4 connectivity: -bindoptions flag is used only for
rebinding a user package and cannot be used for binding
IBM Data Server Driver for JDBC and SQLJ packages. The
DB2Binder does not support -bindoptions for providing
additional bind options beyond those exposed by explicit
individual options when binding JCC packages. Db2Binder
utility will now be able to bind JCC packages with any
"server specific generic options" that are not currently
supported through an external flag, when ?action is
specified as "add" or "replace". (RTC 26270)
Type-4 connectivity: When using an XA Connection,
connection processing may hang during a server outage
preventing failover to available alternate DB2 members to
succeed. In a WebSphere environment, the condition is
marked by WebSphere warning messages that indicate threads
that have been hung for a long time. The thread stack
traces show the thread is waiting in a socket read call.
Socket read is a common driver activity so an
XA Connection and a coinciding server failure are
necessary to be present simultaneously to indicate this
error condition. (RTC 39487)
Type-4 connectivity: Due to best member calculation prior
to flowing any query, a member that initially failed for a
query may get picked again during seamless failover, which
is incorrect. This causes seamless failover failures or
sub-optimal reroute behavior. (RTC 41553)
Type-4 connectivity: During automatic client reroute
against DB2 pureScale, the driver does not retry the
failed member even if all the other known members of the
group are unavailable. This can prevent successful client
reroute in certain situations. (RTC 47801)
Type-4 connectity: An SSL connection to DB2 fails with a
"java.lang.IllegalArgumentException: SSL protocol cannot
be enabled in FIPS/SP800_131/suiteb mode" message when
SP800-131=STRICT setting is configured on the JVM.
(RTC 45793)
Type-4 connectivity: The connectNode property on the
driver is not supported with enableSysplexWLB=true.
However, in such a misconfigured setup, the driver may end
up using transports in a way that causes a DB2 LUW server
to have a panic follwed by a crash.
(RTC 44386)
Type-4 connectivity: An SQL Exception with SQLCODE=-4228
occurs due to an underlying
java.lang.ArrayIndexOutOfBoundsException during failover
from a failing DB2 pureScale member to an available
alternate member. (RTC 41845)
Type-4 connectivity: A NullpointerException may be thrown
by the driver when it is connected to a DB2 pureScale HADR
cluster and a takeover is initiated by the alternate
cluster. (RTC 42754)
All connectivities: An SQL Exception with SQLCODE=-4463
and message "Error parsing FLOAT literal value starting at
index xx. Error Detail:Unexpected character '.' found in
FLOAT literal." is thrown by the driver when an
application specifies a floating point literal containing
a decimal point. For example, a stored procedure call
"CALL SP ('ABC',2,2.3E4,5,5.123)" fails if the third
parameter is of type FLOAT.
All connectivities: At any tracelevel other than
tracelevel of zero, the driver's BLOB tracing mechanism
can consume large amounts of CPU and Memory if the BLOB
data exchanged with the server is huge. (RTC 40884)
Type-4 connectivity: A standalone PREPARE flow to the
server occurs when deferPrepares=false or addBatch( ) api
are used. Such a standalone PREPARE flow does not
seamlessly failover in case the connected server suffers
an outage. This can cause SQL Exception with
SQLCODE=-30108 indicating a non-seamless failover where an
application may be expecting seamless failovers with no
exceptions. (RTC 29263)
All connectivities: If traceFile property value is
supplied through the global db2.jcc.traceFile property and
a traceLevel value is provided on a DataSource, driver
ignores the traceLevel set on the DataSource.
This issue has been fixed. (RTC 40787)
Type-4 Connectivity, Type-2 LUW Connectivity: Added
support to parse query attribute isolation level,
QRYATTISOL DRDA parameter on OPNQRYRM.
Type-4 Connectivity: The JCC Driver will not hold
transport until the end of new unit of work. A possible
symptom is occurrence of SQLException with SQLCODE=-811
which goes away on turning off transport pooling.
(RTC 45936)
All zos Connectivity: An application may receive
SQLCODE181(-181) when it sends a timestamp with date
component as 9999-12-31 or 0001-01-01
(for example 9999-12-31 23:59:59.0) for a timestamp
parameter of a stored procedure using the setObject() api.
This occurs when timezone adjustment on the DB2 server
causes the value to overflow or underflow. This has
been fixed in the JCC driver by omitting TIME ZONE
information in the value sent to the server in case the
date in the timestamp matches 9999-12-31 or 0001-01-01.
(RTC 42217)
All zos Connectivity: Due to a conversion logic error, the
client application may receive ????? from the JCC driver
instead of the actual SQLSTATE string. . This issue is fixed.
(RTC 42728)
All zos Connectivity: DB2 V10 NFM or higher server supports
TIMESTAMP with TIME ZONE type. When application sends data like
9999-12-31 23:59:59.0 to a timestamp column into these DB2
servers results SQLCODE181(-181). This is because by default
the driver was sending TIME ZONE information to the server.
In the boundary values case, the server is not able to process
it. With the current fix, the driver is NOT sending TIME ZONE
information to theserver if the date part is 9999-12-31 or
0001-01-01.(RTC 37158) |
