ORA-01400 Database Error When An SBTransportException Is Thrown On A Composite With Audit Disabled
(Doc ID 1598002.1)
Last updated on APRIL 23, 2019
Applies to:Oracle SOA Suite - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Customer found an scenario where a transport related exception being thrown on a Direct Binding reference leads to the following jdbc exception:
java.sql.BatchUpdateException: ORA-01400: cannot insert NULL into ("DEV_SOAINFRA"."REFERENCE_INSTANCE"."CREATED_TIME")
It looks like it happens when the audit settings are not the same for all of the involved SOA composites.
There are couple of SOA projects to reproduce the problem, the first one (named AuditBug) is deployed with no audit settings (so it is shown as Inherit in EM).
This composite consists on a very simple BPEL that makes a call on a reference on the second composite (named SampleUtilities).
This second composite has an audit level set to off, and has a DirectBinding reference on a *non existent* remote endpoint
(NOTE: This is done on purpose to force a SBTransportException, not an error in the provided sample project.)
The audit level configured in the SOA Infrastructure Common Properties is 'Development', while the level set in the BPEL engine is 'Inherit'
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document