Type-4 connectivity: When the driver is connected to a data
sharing group (sysplex or pureScale), and carrying out an
automatic client reroute, there are situations when the creation
of a TCP/IP
socket to a member of the data sharing group succeeds, but
subsequent flows fail. The driver may not handle such errors
correctly. This problem has been fixed. (31222)
----------------------------------------------------------------
-------------------------------------------
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.(32630)
----------------------------------------------------------------
-------------------------------------------
Type-4 connectivity: This issue occurs when the driver is
working against a pureScale HADR environment that contains two
pureScale clusters, each configured as an alternate the other.
When the
primary group goes into standby and the secondary group takes
over the primary role, the driver does not successfully fail
over to the secondary group, instead returns SQLCODE -1224 to
the calling
application. This problem has been fixed.(29767)
----------------------------------------------------------------
-------------------------------------------
Type-4 Connectivity: When a SQL execution is given up by IBM
DB2 Driver for JDBC and SQLJ driver due to driver hitting the
limit for seamless retries, SQL20542N will now be thrown
instead of
SQLCODE4228 (-4228) with error text "The statement was not
executed because the connection to the database server was
dropped, and the automatic client reroute (ACR) feature failed
to successfully
re-execute the statement." (RTC 32315)
----------------------------------------------------------------
-------------------------------------------
Closing text :SQLJ:When performing SQLJ customization on a
3-tier connection to DB2 10.1 server (via DB2 Connect v9.7
server) connection fails with DRDA data stream syntax error with
SQLCODE4499
(-4499), after rollback is sent on the connection.
[jcc][t4][2034][11148][3.64.106] Execution failed due to a
distribution protocol error that caused deallocation of the
conversation
A DRDA Data Stream Syntax Error was detected. Reason: 0x1900.
ERRORCODE=-4499, SQLSTATE=58009 The problem is not reproducible
with a direct connection. This problem is fixed. (RTC 33509)
----------------------------------------------------------------
-------------------------------------------
Type-4 Connectivity: IBM DB2 Driver for JDBC and SQLJ driver
throws a null pointer exception if currectPackageSet is not set
and runJDBCBinder is invoked .
Exception in thread "main" java.lang.NullPointerException
at
com.ibm.db2.jcc.am.Connection.setCurrentPackageSetX(Connection.j
ava:3790)
at
com.ibm.db2.jcc.am.Binder.runJDBCBinderFromAPI(Binder.java:404)
(RTC 30250)
----------------------------------------------------------------
-------------------------------------------
Type-4 Connectivity: Some of the dummy error location numbers
in IBM DB2 Driver for JDBC and SQLJ driver are updated with
correct error location numbers.
(RTC 30548)
----------------------------------------------------------------
-------------------------------------------
Type-4 Connectivity: While db2binder utility uses -bindOptions
, API invocation uses -bindoptions. Changes are made in IBM DB2
Driver for JDBC and SQLJ driver so that API invocation usage is
in
sync with db2binder. (RTC 31032)
----------------------------------------------------------------
------------------------------------------
T4 Connectivity: When keepAliveTimeout is set to zero the
driver does not use the operating system default parameters for
keep alive behavior. . The problem has been fixed .(APAR
IC93280 )
----------------------------------------------------------------
-------------------------------------------
All connectivity: Warning thrown when user tries to set
unsupported client information using
Connection.setClientInfo(Properties) method did not include the
token name to help identify the
supported token. The problem has been fixed and the warning now
includes the unsupported client information token.(29581)
----------------------------------------------------------------
-------------------------------------------
Type-4 connectivity: With useCachedCursor=true, an SqlException
with ERRORCODE=-4228 occurs after the table being queried has
been altered and the executeQuery method of PreparedStatement
has
been called with JCC3.67.
This APAR makes the following changes if the database server is
DB2 for Linux, UNIX and Windows:
1.The default value of the JCC property useCachedCursor is
false.
2.If the JCC property deferPrepares is true then the JCC driver
always behaves as if the JCC property useCachedCursor is
false. APAR (IC92609)
----------------------------------------------------------------
-------------------------------------------
Type-4 connectivity: In case of TLS certificate authentication,
JCC will treat emplty password as NULL
----------------------------------------------------------------
-------------------------------------------
All connectivity: NULLPOINTER EXCEPTION OCCURS WHEN EXECUTING A
BATCH CONTAINING AN SQL WITH A 'INSERT FROM SELECT CLAUSE'
This is a customer reported issue (0227173 - PRM only - Fiducia
Infor ). PMR (02934,073,724 ) APAR number (IC92930 ).
It has been fixed in 4.17 and 3.67.
----------------------------------------------------------------
-------------------------------------------
All connectivity: Customer gets NullPointerException if they set
System.err to null (System.setErr(null)) and try to connect to
z/OS server using temporary license file
This is a customer reported issue (7916880 - SAP DB2 CONNECT
(OEM) ). PMR number (46641,724,724), APAR number IC92579. It has
been fixed in 4.17 and 3.67.
----------------------------------------------------------------
-------------------------------------------
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 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 case of reuse JCC closes all the open
statements, which can cause start of a new transaction on
server. This results in the connection unfit to be reused. (RTC
25374)
----------------------------------------------------------------
-------------------------------------------
Type-4 Connectivity: A batch update may fail if its using
setDBStringAsByte to set Unicode text and the first row of the
same batch had null for the same column. (RTC 31674)
----------------------------------------------------------------
-------------------------------------------
All connectivity: While setting Current_LC_Type property, server
is ignoring the property and it's throwing the warning message
(+799) as below. And also setting the default values for
property.
Property: ((com.ibm.db2.jcc.DB2BaseDataSource)
ds).setCurrentLocaleLcCtype("En_US"); The fix is to modify the
register name from CURRENT_LC_CTYPE to CURRENT LOCALE LC_CTYPE
which is accepted by
DB2 Z Server.The problem has been fixed. (33638)
----------------------------------------------------------------
-------------------------------------------
All connectivity: SqlSyntaxErrorException: Invalid argument:
Parameter marker 'OUTPARM ' was not present in the SQL String.
This exception was getting thrown if the Parameter marker name
contains
space before or at the end.Property:
db2cs.registerJccOutParameterAtName("OUTPARM ",
java.sql.Types.ARRAY); The fix is to trim the parametermarker
name so that it truncates any extra spaces.
The problem has been fixed. (22931) |
