DB2 - Problem description
Problem IC98852 | Status: Closed |
CONCURRENTACCESSRESOLUTION DS DRIVER KEYWORD DOES NOT TAKE EFFECT IF VALUE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
The data server driver configuration parameter ConcurrentAccessResolution does not work if the value is specified by string like 'CurrentlyCommitted'. The parameter works if the value is set as the same as CLI/ODBC parameter like '1'. The following example illustrates the problem. a) This settings does not work to set currently committed for the connection. <database name="SAMPLE" host="localhost" port="50000"> <parameter name="ConcurrentAccessResolution" value="CurrentlyCommitted"/> </database> b) This settings can be used for workaround. <database name="SAMPLE" host="localhost" port="50000"> <parameter name="ConcurrentAccessResolution" value="1"/> </database> As Information Center says the Data Server driver uses string values for this parameter except 0, and the Data Server driver values should be converted to CLI/ODBC values by Data Server driver. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users who use ConcurrentAccessResolution Data Server driver * * keyword. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Please upgrade to V10.1 FixPack 4 or later. * **************************************************************** | |
Local Fix: | |
Please use value 1 for CurrentlyCommitted, 2 for WaitForOutcome. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
This problem was first fixed in DB2 V10.1 FixPack 4 or later. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC99054 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.01.2014 16.06.2014 16.06.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |