Problem with Trigger in TransactionScope

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
Posts: 7
Joined: Wed 12 Oct 2011 12:33

Re: Problem with Trigger in TransactionScope

Post by teddyFry » Mon 21 Jan 2013 09:54

I've got the network 200 error with dotconnect v7.2 and I open transaction like that :

Code: Select all

using (TransactionScope ts = new TransactionScope(TransactionScopeOption.Required, new TransactionOptions { IsolationLevel = IsolationLevel.ReadUncommitted }))
But it seems that it's a normal behavior of Oracle witch is not supporting ReadUncommited

Devart Team
Posts: 2141
Joined: Wed 02 Nov 2011 09:44

Re: Problem with Trigger in TransactionScope

Post by Pinturiccio » Fri 25 Jan 2013 13:54

We cannot reproduce the "Network error : 200" error with dotConnect for Oracle 7.2. To investigate the issue, we need a test example reproducing the "Network error : 200" exception. Please create and send us a small test project with the corresponding DDL/DML scripts for reproducing the issue.
Please also describe the steps we have to perform to get the exception.

When using your code, we gen the following exception: "Transaction isolation level ReadUncommitted not supported.", which is a designed behavior.

Post Reply