Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC71913 Status: Closed

DOCUMENTATION OF CHANGES IN IBM DATA SERVER DRIVER FOR JDBC AND SQLJ
VERSION JCC 3.61.86/4.11.88 FOR DB2 LUW V9.5 FIXPACK 7

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
This is the first APAR. We included more APAR's since the 
closing 
text exceeded the limit. 
 
============================================================ 
All Connectivity Type: Previously, setObject with value 
null for static path would fail with SQLException "Invalid 
data conversion: Parameter instance null is invalid for 
 the requested conversion". Now Jcc allows setObject 
with null for static path if it's not for zOS stored procedure. 
(140483) 
 
____________________________________________________________ 
T4 Connectivity Type: If client reroute is configured 
and queryTimeOut is set, if primary server goes down 
and application reroutes to the alternative server, 
the application may hang. This problem is fixed. 
(141179) 
 
____________________________________________________________ 
T4 Connectivity: When enableSysplexWLB is true, 
securityMechanism sets to one of the encryption security 
mechanism, and the encryptionAlgorithm is AES (the 
encryptionAlgorithm could set to AES explicitly or 
the driver uses AES for default if server supports 
AES), the driver may throw the following Exception: 
"Connection authorization failure occurred.  Reason: 
User ID or Password invalid. ERRORCODE=-4214, 
SQLSTATE=28000" The problem is fixed.(143884) 
 
____________________________________________________________ 
T4 Connectivity: When Statement.cancel() is called 
(this could be called by the application explicitly 
or implicitly), if multithreading is involved, a 
NullPointerException might occur. This problem is fixed. 
(144207) 
 
____________________________________________________________ 
SQLJ All Connectivity types: An ArrayIndexOutOfBounds exception 
occurs when statement caching is turned on under WebSphere 
6.1, and a single SQLJ statement is executed in both 
batched and non-batched execution paths. (142179) 
 
____________________________________________________________ 
All Connectivity Type: 
When retrieveMessagesFromServerOnGetMessage sets to true, if 
the package is not found, SQLException with error code 
-805 will be issued. SQLException.getMessage may cause 
java.lang.StackOverflowError. The problem is fixed. 
(wsdbu00670958 wsdbu00670963) 
 
____________________________________________________________ 
T4 Connectivity Type: In Sysplex environment, if the 
application sets the securityMechanism to 
ENCRYPTED_PASSWORD_SECURITY and DB2 server supports 
AES, getting Connection may fail sporadically 
with SQLException -4214. The problem has been fixed. 
(wsdbu00668088 wsdbu00668091) 
 
____________________________________________________________ 
All Connectivity Type: if the server is i5 server, 
and progressive lob locator is used as input parameter, 
SQLException with error code -423 may be issued. The 
problem is fixed. (wsdbu00664162 wsdbu00664164) 
 
____________________________________________________________ 
All Connectivity Type: Jcc now does range checking 
on DataSource property updateCountForBatch and 
cursorSensitivity. If the property sets to values 
other than 0, 1, or 2, Jcc will throw Exception. 
(wsdbu00661126 wsdbu00661167) 
 
____________________________________________________________ 
T4 Connectivity Type: If client reroute is configured 
and queryTimeOut is set, if primary server goes down 
and application reroutes to the alternative server, 
the application may hang. This problem is fixed. 
(wsdbu00643556 wsdbu00657199) 
 
____________________________________________________________ 
All Connectivity Type: Previously, setObject with value 
null for static path would fail with SQLException "Invalid 
data conversion: Parameter instance null is invalid for 
 the requested conversion". Now Jcc allows setObject 
with null for static path if it's not for zOS stored procedure. 
(wsdbu00643367 wsdbu00654204) 
 
____________________________________________________________ 
All Connectivity Type: 
The ClientDebugInfo support is enabled for IDS Panther 
and above release. ClientDebugInfo can be set using 
property clientDebugInfo or using the following 
DB2Connection APIs: 
public void setDB2ClientDebugInfo(String debugInfo) 
  throws java.sql.SQLException 
public void setDB2ClientDebugInfo(String mgrInfo, 
  String traceInfo) 
(wsdbu00651351 wsdbu00651724) 
 
____________________________________________________________ 
All Connectivity: Tracing system property "sun.java.command" 
is incorrectly performed. It only occurs when invoking a java 
program from a .bat file uisng JDK16. (wsdbu00672204) 
 
____________________________________________________________ 
All Connectivity: DBTimestamp error message prints out 
the wrong ISO format: 
"yyyy-mm-dd.hh.mm.ss[.ffffffffffff][ ](+|-)th:tm 
 yyyy-mm-dd.hh.mm.ss[.ffffffffffff]". 
The driver behavior is implemented correctly. 
The error message has been corrected to 
"yyyy-mm-dd-hh.mm.ss[.ffffffffffff][ ](+|-)th:tm 
 yyyy-mm-dd-hh.mm.ss[.ffffffffffff]". (wsdbu00654941) 
 
____________________________________________________________ 
All Connectivity Type: When the property 
stripTrailingZerosForDecimalNumbers is in effect, positive 
decimal numbers may be shown in exponential notation, 
which does not conform to what Java doc indicates.  Now 
the problem is fixed.  (142035, wsdbu00653222) 
 
____________________________________________________________ 
T4 Connectivity: The type 4 driver does not set all 
java.sql.BatchUpdateException's update counts to -3 
( java.sql.Statement.EXECUTE_FAILED) although at least 
one of the atomic batch Multi-row insert operations 
fails. The fix alters the behavior by setting all values 
in the update counts to -3 if any of the atomic batch 
Multi-row insert operations fails.(146369) 
 
____________________________________________________________ 
T4 Connectivity: Include maxTransportObjects property in 
jcc trace. (wsdbu00656892) 
 
____________________________________________________________ 
All Connectivities: A new datasource/connection boolean property 
useIdentityValLocalForAutoGeneratedKeys is introduced to 
determine auto-generated key values.  A value of true indicates 
that the driver must use the database IDENTITY_VAL_LOCAL() 
function to determine the auto-generated keys values. 
A value of false indicates that the driver may exploit 
alternative 
database supported methods, such as SELECT FROM INSERT to 
determine 
the auto-generated key values. The default is false. (146420) 
 
____________________________________________________________ 
All Connectivities: When the DELIMIDENT variable is turned 
on in IDS and quoted column names are used to specify the 
auto generated keys column names, the driver is throwing 
a SQLException with -4461 SQL code. (wsdbu00671428) 
 
____________________________________________________________ 
All Connectivities:  When SQLCODE -911 is returned from DB2 
LUW server, while accessing the result set returned for a 
select statement, a null pointer exception is thrown by the 
driver. (wsdbu00665571) 
 
____________________________________________________________ 
All Connectivities: PreparedStatement.setCharacterStream () 
throws an indexoutofbounds exception for an XML document 
greater than 1GB. (wsdbu00642607)
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.5 Fixpack 7                            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problems fixed in DB2 LUW V9.5 Fixpack 7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.10.2010
25.05.2011
25.05.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.7 FixList
9.5.0.7 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.