CALLING COMPLETE ON A TRANSACTIONSCOPE OBJECT FAILS TO COMMIT DATA TO ORACLE WHEN A SQL SERVER CONNECTION IS INVOLVED AND IS THE FIRST TO ENLIST (Doc ID 1491873.1)

Last updated on SEPTEMBER 21, 2012

Applies to:

Oracle Data Provider for .NET - Version 11.2.0.1 and later
Information in this document applies to any platform.

Symptoms

Calling TransactionScope.Complete() on a TransactionScope object fails to commit the data to the Oracle database when a SQL Server connection is the first to enlist. If Oracle enlist first followed by SQL Server, then all data is committed properly.

For Example:

 

Changes


Cause

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