Follow Us on Twitter

SOA DbAdapter lingo: java.sql.SQLException: setObject, Exception = 8

by Laurens van der Starre on September 18, 2014 · 0 comments

In the many years that I work with the Oracle SOA Suite and its Database Adapter, I never really had the pleasure of encountering the setObject errors.

Normally when you screw up the IN parameters in your call to the Database Adapter you’d get those java struct  “cannot convert STRING to NUMERIC” errors. However, the following message

Set object error.
Error binding the value of parameter P_SOMEINPUT.
An error occurred when binding the value of parameter P_SOMEINPUT in the ABC.SOMEPACKAGE.INS API. Cause: java.sql.SQLException: setObject, Exception = 8
Check to ensure that the parameter is a valid IN or IN/OUT parameter of the API.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.

is just the same, only more vague (and not really on Google … 🙂 ).

You have to check your IN parameters. Get them from the audit trail als validate it against the XSD generated by the adapter. (Use for example this one).

Most probably there is some nill date or decimal element in your input.


VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

{ 0 comments… add one now }

Leave a Comment


Previous post:

Next post:

About Whitehorses
Company profile

Whitehorses website

Home page

Follow us
Blog post RSS
Comment RSS