This post originated from an RSS feed registered with Java Buzz by Simon Brown. Original Post: Enabling XA support in Oracle Feed Title: Simon Brown's weblog Feed URL: http://www.simongbrown.com/blog/feed.xml?flavor=rss20&category=java Feed Description: My thoughts on Java, software development and technology. Latest Java Buzz Posts Latest Java Buzz Posts by Simon Brown Latest Posts From Simon Brown's weblog

We've been trying to get XA transactions working across resources including an Oracle 9.0.2.x database and while this seems easy to configure in WebSphere Application Server, we've been seeing some rather unhelpful error messages at runtime, including the following:

• SQLException: SQLState(65000) vendor code(6550)
  java.sql.SQLException: ORA-06550: line 1, column 13:
  PLS-00201: identifier 'JAVA_XA.XA_START_NEW' must be declared
  ORA-06550: line 1, column 7:
  PL/SQL: Statement ignored

• The XA Error is            : -3
  The XA Error message is    : A resource manager error has
                               occured in the transaction branch.
  The Oracle Error code is   : 65535
  The Oracle Error message is: Internal XA Error
  The cause is               : null.

After a fair amount of googling, we stumbled upon an answer here basically saying that you need to "enable" XA on the database with some SQL scripts. I hope that this helps somebody else in the future as it wasn't all that easy to track down an answer to!