Invalid Objects Created while Calling Hxc_timestore_deposit.execute_deposit_process from SOA (Doc ID 1641882.1)

Last updated on APRIL 01, 2014

Applies to:

Oracle(R) BPEL Process Manager - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

11.1.1.6.0 version, BPEL Runtime

Invalid objects created while calling hxc_timestore_deposit.execute_deposit_process from SOA.

Using the Oracle OTL API:Execute_deposite_process to build a composite with Apps Adapter. The sql:XX_BPEL_PLKAPPS_EXECUTE_DEPOSI.sql generated from APPs Adapter shows an invalid staus from Toad. If using the same api without using SOA it works fine. The problem seems to be caused by an invalid wrapper created by JDeveloper.



XX_BPEL_PLK_APP_EXECUTEDEPOSIT(body) ....Status:Invalid

Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Block cannot handle exception.
failure of the block "Bp" to handle a business exception for the instance "840070"; exception reported is: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
...
An error occurred while preparing and executing the xxx API. Cause: java.sql.SQLException: ORA-04063: package body "xxx" has errors
ORA-06508: PL/SQL: could not find program unit being called: "xxx"
ORA-06512: at line 1

Check to ensure that the API is defined in the database and that the parameters match the signature of the API. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-4063" 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.
".
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.

,detail=ORA-04063: package body "xxx" has errors
ORA-06508: PL/SQL: could not find program unit being called: "xxx"
ORA-06512: at line 1

,code=4063}

This error contained the exceptions thrown by the underlying routing system.
Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).

ORABPEL-05002



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