Skip to Main Content

Developer Community

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!

How to expose Oracle DB runtime errors (e.g., ORA-01109: database not open) in BPEL?

Sharmin Sultana2 days ago

I am working with Oracle SOA Suite 12c (12.2.1.3). In my BPEL process, I am invoking a Database Adapter.

If the database is shut down, in SQL Developer I see the error:

ORA-01109: database not open

But in BPEL / Enterprise Manager / Postman, I only see a generic remote fault like:

Cannot obtain XAConnection

If the database user credential is changed, in SQL Developer I see the error:

ORA-01017: invalid username/password; logon denied

But in BPEL / Enterprise Manager / Postman, I only see a generic binding fault like:

Cannot acquire data source

I have exposed my BPEL process as a REST service and I am testing it using EM,Postman. I want to expose the actual ORA-xxxx error message (for example, ORA-01109) back to the BPEL client response.

My question:

👉 Is it possible to expose the actual Oracle ORA-xxxx error (e.g., ORA-01109) to the BPEL client?

👉 If yes, how can I capture and return the full DB error text?

Environment:

  1. Oracle SOA Suite 12.2.1.3
  2. Database Adapter in BPEL

I handled remoteFault and bindingFault using catch blocks inside the BPEL process.

I tried using fault-policies.xml and fault-bindings.xml with actions like ora-retry and ora-rethrow-fault.

I also experimented with changing the audit log configuration to see if the full ORA-xxxx message could be exposed.

I expected these configurations to capture the original Oracle error (e.g., ORA-01109: database not open) and return it in the BPEL client response. But in all cases, I still only get the generic error messages such as Cannot obtain XAConnection or Cannot acquire data source.

Comments
Post Details
Added 2 days ago
2 comments
27 views