DB2 FOR LUW / DB2FORLUW / 970 - 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 9.7 Fix Pack 10.                      * 
****************************************************************

First fixed in DB2 Version 9.7 Fix Pack 10.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC97248 IC97249 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

28.10.2013
11.11.2014
11.11.2014

9.7.FP10