Skip to Main Content
Forums

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Using DB links in Stored proc call in DB adapter 11G SOA

user626262May 31 2010 — edited Jan 27 2011
Hi
We are using Oracle 11G SOA Suite and have created a DB adapter which has a call to stored procedure . The stored proc has sql queries to access remote DB using db links. The DB link has been created in our local database pointing to another schema where the tables are residing.
When executing this we get the following error

ORA-24777: use of non-migratable database link not allowed

Can anybody provide solution to this ?

Thanks
This post has been answered by Anuj Dwivedi-Oracle on Jun 2 2010
Jump to Answer

Comments

Anuj Dwivedi-Oracle
Answer
Hi,

Can you provide more details? Which driver are you using? Is it XA or non-XA? If you are using XA then try using non-xa.

Cross post this question in SOA suite forum as well -

3322

Regards,
Anuj
Marked as Answer by user626262 · Sep 27 2020
user626262
thanks anuj . It worked while we created a non XA db source. Any specific reason why it worked while using NON XA ?
Anuj Dwivedi-Oracle
ORA-24777: use of non-migratable database link not allowed
Cause: The transaction, which needs to be migratable between sessions, tried to access a remote database from a non-multi threaded server process.
Action: Perform the work in the local database or open a connection to the remote database from the client. If multi threaded server option is installed, connect to the Oracle instance through the dispatcher.

An XA transaction involves a coordinating transaction manager, with one or more databases (or other resources, like JMS) all involved in a single global transaction. Non-XA transactions have no transaction coordinator, and a single resource is doing all its transaction work itself (this is sometimes called local transactions).

Regards,
Anuj
596264
I really just want to use one generic adapter, with XA transaction enabled, for all of my database connections. I have a simple BPEL process that selects data - why should I have to use a non-XA datasource for this process? Are there any other workarounds for this? Some way of forcing a transaction manager for single transactions maybe?
1 - 4
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Feb 24 2011
Added on May 31 2010
#applications-integration-using-oracle-fusion-middleware, #soa-process-management
4 comments
2,803 views