java.sql.SQLException: ORA-06550: line 1, column 15: PLS-00904: insufficient privilege to access object SOADEMO.SP_QUERY ORA-06550: line 1, column 7: PL/SQL: Statement ignored 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 "-6550" 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.

Oracle Community | jaiya | 4 years ago
  1. 0

    Reg: Need help to call a Stored Procedure - Out Parameter using DBAdapter

    Oracle Community | 4 years ago | jaiya
    java.sql.SQLException: ORA-06550: line 1, column 15: PLS-00904: insufficient privilege to access object SOADEMO.SP_QUERY ORA-06550: line 1, column 7: PL/SQL: Statement ignored 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 "-6550" 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.
  2. 0

    Unable to Invoke a storedProc From OSB

    Oracle Community | 5 years ago | 885531
    java.sql.SQLException: ORA-04068: existing state of packages has been discarded ORA-04063: package body "APPS.BPEL_ORAAPPSDEV" has errors ORA-06508: PL/SQL: could not find program unit being called 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 "-4068" 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.
  3. 0

    BEA-382500: OSB Service Callout action received SOAP Fault response

    Oracle Community | 5 years ago | Mani
    java.sql.SQLException: ORA-01403: no data found ORA-06512: at "PROCD_PATIENTENRICHMENT", line 3 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 "-1403" 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.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    BEA-382500: OSB Service Callout action received SOAP Fault response

    Oracle Community | 5 years ago | Mani
    java.sql.SQLException: ORA-01403: no data found ORA-06512: at PROCD_PATIENTENRICHMENT", line 3 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 "-1403" 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.
  6. 0

    JCA Transport Database Errors catching/understanding.

    Oracle Community | 6 years ago | 782468
    java.sql.SQLException: ORA-01013: user requested cancel of current operation ORA-06512: at "SINGLE_OSB_DOMAIN_VM1.CUSTOMER_TRIGGER", line 2 ORA-04088: error during execution of trigger 'SINGLE_OSB_DOMAIN_VM1.CUSTOMER_TRIGGER' ORA-06512: at "SINGLE_OSB_DOMAIN_VM1.TIMEOUTED_PROC", line 5 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 retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "1013" 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.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.sql.SQLException

      ORA-06550: line 1, column 15: PLS-00904: insufficient privilege to access object SOADEMO.SP_QUERY ORA-06550: line 1, column 7: PL/SQL: Statement ignored 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 "-6550" 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.

      at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation()
    2. oracle.sysman.emas
      WSView.invokeOperation
      1. oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:808)
      2. oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:384)
      2 frames