Experiencing Error ORA-01013 when access Oracle database

Solution Verified - Updated

Environment

  • Enterprise Application Platform (EAP)
    • 4.3.0 CP7
    • 5.1.2
  • Oracle

Issue

We have encountered the following error in JBoss, do you have idea why it happens ?

java.sql.SQLException: ORA-01013: user requested cancel of current operation
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210)
at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:804)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1049)
at oracle.jdbc.driver.T4CStatement.executeMaybeDescribe(T4CStatement.java:845)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1154)

Resolution

Increase the value of the transaction/query timeout

Root Cause

Customer had decreased the length of the query timeout, and it was too low.

Diagnostic Steps

Oracle docs explains on ora-01013 error[1], ORA-01013 is known as an "information" error.  It is letting you know that the operation has been cancelled by either:

  • Caused by the user (pressing CTRL-C or a different method like front-end application),
  • Caused by a response to congruent errors OR
  • The result of timeouts.

Resolving ORA-01013 is dependant upon the reason for the  operation to terminated.  If ORA-01013 signifies that the operation has been explicitly shut down by the user, the error in simply informational and there is nothing that can be done, other than proceeding to the next operation. 

Content from www.dba-oracle.com is not included.

What should I do if I am facing this issue in my application[2]?
Follow these simple steps:

  • First make sure that your query can be completed within the timeout that you have specified. If you consistently face this exception, try increasing your timeout.
  • That might help to get rid of the exception, but not the root cause. The root cause usually is a database that is not optimized for the query that you are executing or a bad network.
  • To find out if its the database that is the issue, try executing the same query in a host closer to the network. Or try executing the same query hitting the database from a different network. If you are convinced the database is the issue, try to tune it.
  • To find if it is the network that is having the issue, try to do a tcpdump and analyze if there are any out of order deliver of packets. Or dropped packets. If yes, then try to fix the network.

[1] Content from www.dba-oracle.com is not included.Content from www.dba-oracle.com is not included.http://www.dba-oracle.com/t_ora_01013_user_requested_cancel_of_current_operation.htm

[2] Content from royontechnology.blogspot.com is not included.http://royontechnology.blogspot.com/2009/06/mysterious-ora-03111-error.html

SBR
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.