DB Adapter Exception not Translated. DB Adapter Fault not Caught by Catch or Catchall (Doc ID 434695.1)

Last updated on JULY 29, 2008

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.1
This problem can occur on any platform.

Symptoms

A 10.1.2 BPEL process using the DB adapter, used to throw a binding Fault if you tried to insert a
string too long for a column or in other words if you have a SQL error.


The same process under 10.1.3 does not throw a binding Fault. This leads to the exception not being caught by the BPEL Process in the Catch or Catchall branches. When the BPEL process is initiated from the BPEL console, it ends with this error in the "Initiate" tab :

Value: <Faulthttp://schemas.xmlsoap.org/soap/envelope/>
<faultcode>env:Server</faultcode>
<faultstring>java.sql.BatchUpdateException: ORA-12899: value too large for column
"APPS"."XX_TEST"."COLUMN2" (actual: 16, maximum: 10) </faultstring>
</Fault>


-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:

1. Create a BPEL process that uses the DB Adapter to insert a row into a table.
2. From the BPEL console, initiate an instance with a string that is too long to fit into the column.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms