java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation ORA-06512: at "SYS.DBMS_LOCK", line 201 ORA-06512: at "HR.PROC_DELAY1", line 7 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. Because the global transaction is rolling back the invoke must be retried in a new transaction, restarting from the place of the last transaction commit. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "1013" to your deployment descriptor (i.e. weblogic-ra.xml).

Oracle Community | sairamk | 2 years ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    CatchAll block not catching JTA timeout with XA datasource

    Oracle Community | 2 years ago | sairamk
    java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation ORA-06512: at "SYS.DBMS_LOCK", line 201 ORA-06512: at "HR.PROC_DELAY1", line 7 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. Because the global transaction is rolling back the invoke must be retried in a new transaction, restarting from the place of the last transaction commit. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "1013" to your deployment descriptor (i.e. weblogic-ra.xml).

    Root Cause Analysis

    1. java.sql.SQLTimeoutException

      ORA-01013: user requested cancel of current operation ORA-06512: at "SYS.DBMS_LOCK", line 201 ORA-06512: at "HR.PROC_DELAY1", line 7 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. Because the global transaction is rolling back the invoke must be retried in a new transaction, restarting from the place of the last transaction commit. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "1013" to your deployment descriptor (i.e. weblogic-ra.xml).

      at oracle.tip.adapter.db.exceptions.DBResourceException.createXARetriableException()
    2. oracle.tip.adapter
      DBInteraction.execute
      1. oracle.tip.adapter.db.exceptions.DBResourceException.createXARetriableException(DBResourceException.java:686)
      2. oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:658)
      3. oracle.tip.adapter.db.sp.SPUtil.createResourceException(SPUtil.java:180)
      4. oracle.tip.adapter.db.sp.AbstractStoredProcedure.execute(AbstractStoredProcedure.java:131)
      5. oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:142)
      6. oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:1167)
      7. oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:254)
      7 frames
    3. oracle.integration.platform
      JCAInteractionInvoker.executeJcaInteraction
      1. oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:357)
      1 frame