Latest versionsfixlist
11.1.0.7 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

DB2 - Problem description

Problem IT03806 Status: Closed

JCC: SQL_ATTR_CONCURRENT_ACCESS_RESOLUTION IGNORED FOR EMBEDDED SELECTS

product:
DB2 DATA SRVR D / DB2DSDRVR / A10 - DB2
Problem description:
With database configuration CUR_COMMIT set to AVAILABLE and 
making use of setDBConcurrentAccessResolution setting the 
property SQL_ATTR_CONCURRENT_ACCESS_RESOLUTION, 
an application will hang with the following query if there is an 
uncommitted update on table yyy: 
 
INSERT INTO xxx (SELECT , , FROM yyy) 
 
Currently the JCC driver only applies and uses "USE CURRENTLY 
COMMITTED" attribute if it recognizes and SQL as a purely SELECT 
SQL. 
 
This APAR will address this behaviour and allow the driver to 
send the attribute when there are embedded Selects.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of IBM Data Server Driver for JDBC and SQLJ        * 
* shipped with DB2 10.1 releases earlier than DB2 10.1 Fixpack * 
* 5                                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Refer error description                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fixpack 5                                * 
****************************************************************
Local Fix:
Set CUR_COMMIT on database configuration
Solution
Upgrade to DB2 10.1 Fixpack 5
Workaround
Set CUR_COMMIT on database configuration
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.08.2014
22.07.2015
22.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList