|
Problem IC97249
|
Status: Closed |
THE CONNECTION ISOLATION LEVEL IS NOT PRESERVED AFTER A TRANSACTION BUT RE-SET TO THE PRODUCT DEFAULT. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fix Pack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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
|
| Solution |
First fixed in DB2 Version 10.5 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.10.2013
10.09.2014
10.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
