home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC98852 Status: Geschlossen

CONCURRENTACCESSRESOLUTION DS DRIVER KEYWORD DOES NOT TAKE EFFECT IF VALUE
IS SPECIFIED BY STRING.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
This problem was first fixed in DB2 V10.1 FixPack 4 or later.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC99054 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.01.2014
16.06.2014
16.06.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList