This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: Enterprise Services with Oracle 9i Issues
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
I recently posted on our usage of Enterprise Services and Transaction Enlistment. When I designed the overall architecture, I made a strategic decision to go with Oracle's data provider ODP.NET instead of the Microsoft provided one in 1.1, as it has greater performance and more features. This hasn't been a real issue for us: I ported a DAAB to this Oracle provider and we partied on. Recently, some issues have come with Enterprise Services and Oracle particuarly on the Windows 2003 Server platform rather than 2000 and XP in regards to Distributed Transactions and the MSDTC. Robert has been doing some phenominal work for us in the last few days trying to track this down as our dev lead on ES. Oracle, of course, uses XA transactions which are a bit different than Microsoft's. There have been some changes in security for Win2K3 for the DTC and XA transactions. requring one to explicitly enable XA transactions, as well explicitly add an XADLL registry entry that contains your resource manager's XA transaction manager dll. This is all a good thing but after following these steps we are still unable to get things to work. Robert has all the nasty details here. We have searched the Web everywhere and it doesn't seem like too many people are doing ES with Oracle, on a different box than the app server and business logic, with Win2K3 or at least writing about it. We have a hack but it takes the MS DTC out of the picture and can't be right. We are wondering if anyone else has encountered these issues (or better yet come up with some solutions). You can post a comment on Robert's blog or send me email if you desire.
Previous Topic
