ODP.Net bug

Jun 4, 2007 at 8:54 PM
ODP.NET provider has issues under XP, MS Oracle provider works fine. Needs investigation.

Can you explain more on issues with XP and ODP.Net?

Jun 7, 2007 at 2:07 PM

On the XP system I'm currently working on I get...

Unable to enlist in a distributed transaction while the Oracle trace file tells me

ORA-02048: attempt to begin distributed transaction without logging

I suspect it revolves around EnlistTransaction attempting to configure a distributed transaction (although it's not needed but that's all ODP.NET currently supports)... It may very well be my environment, but that ORA error is described as being an internal error so it looks like the DB is what is causing the problem!


Jun 7, 2007 at 6:55 PM
I get the same issue when I try to use ODP.Net with XP sp2
Jul 10, 2007 at 8:04 PM
Edited Jul 10, 2007 at 8:11 PM
Looking at the code, it appears the 'Enlist' connection string parameter is being set to 'false'.

This parameter takes a Boolean value for System.Data derived connections. For ODP, the allowed values are 'true', 'false' and 'dynamic'.

This will always cause the above exception to be thrown by Oracle.DataAccess.Client.OracleConnection

Set this parameter value to 'dynamic' so that the connection can be enlisted when required

Jul 11, 2007 at 12:03 AM
Thanks Chris, I'll give it a go!