ExecuteNonQuery Commits Work Immediately Despite .NET Transaction Is In Aborted State
(Doc ID 1634046.1)
Last updated on FEBRUARY 16, 2019
Applies to:Oracle Data Provider for .NET - Version 126.96.36.199 and later
Executing a call to ExecuteNonQuery to submit DML inside a .NET TransactionScope (distributed transaction) that is in an aborted state results in ODP.NET committing data when an exception should be raised.
For Example, the following simple test case demonstrates the issue:
1. DDL to create the table and populate.
The data is committed but should not be.
SQL> select * from test;
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document