DB2 FOR LUW / DB2FORLUW / A50 - DB2

You have a .NET application that, in the connection string 
specifies the isolation level wanted for a connection like in: 
 
     IsolationLevel=RepeatableRead; 
 
If an explicit transaction is started, with its own TX level 
isolation, once completed, the connection isolation level is not 
put back to the level specified in the connection string 
(RepeatableRead, in the example) but instead it becomes 
CommittedRead. which would be default if no isolation level was 
specified in the connection string.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 4.                      * 
****************************************************************

DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 10.5 Fix Pack 4.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

28.10.2013
10.09.2014
10.09.2014