ExecuteNonQuery Commits Work Immediately Despite .NET Transaction Is In Aborted State
Last updated on MARCH 10, 2014
Applies to:Oracle Data Provider for .NET - Version 220.127.116.11 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;
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms