DB2 - Problem description
Problem IC72592 | 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: | |
We have three APARs for this delivery (IC71913, IC72339, IC72592) This is the third APAR. We included three APAR's since the closing text exceeded the limit. ============================================================ 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,wsdbu00687778) ____________________________________________________________ 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. (wsdbu00686193) ____________________________________________________________ T4 Connectivity Type: JCC driver reports SQLCODE4228 (-4228) when DB2 returns some rows of data and an error for a query. While reporting -4228 JCC driver is also masking the error reported by DB2 which has been fixed in this defect so it actually returns the DB2 error instead. (wsdbu00691169) ____________________________________________________________ All connectivity types: A new property "useIdentityValLocalForAutoGeneratedKeys" is introduced to pecifies whether the IBM Data Server Driver for JDBC and SQLJ uses only the SQL built-in function IDENTITY_VAL_LOCAL to determine automatically generated key values. The data type of this property is boolean. Possible values are: - true: Specifies that the IBM Data Server Driver for JDBC and SQLJ always uses the SQL built-in function IDENTITY_VAL_LOCAL to determine automatically generated key values. The driver uses IDENTITY_VAL_LOCAL even if it is possible to use SELECT FROM INSERT. Specify true if the target data server supports SELECT FROM INSERT, but the target objects do not. For example, SELECT FROM INSERT is not valid for a table on which a trigger is defined. - false: Specifies that the IBM Data Server Driver for JDBC and SQLJ determines whether to use SELECT FROM INSERT or IDENTITY_VAL_LOCAL to determine automatically generated keys. false is the default. (wsdbu00686072) ____________________________________________________________ Type-4 XA Connectivity: A SQLException with SQLCODE911 (-911) was thrown when TMLCS (loosely coupled flag) is used with the XA Start method against DB2 LUW. The problem is fixed. (wsdbu00690521) ____________________________________________________________ SQLJ T4 Connectivity Type: Specifying pkgVersion AUTO during SQLJ Customization will create packages with version of the form: YYYY-MM-DD.HH.MM.SS.nnnn This has changed from the current AUTO generated package version String which generates 3 fractional digits for the seconds. (146461, wsdbu00687385 ) ____________________________________________________________ | |
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 | |
Solution | |
Problems fixed in DB2 V9.5 FIXPACK 7 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.11.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 | |
9.5.0.7 |