ORA-01013: user requested cancel of current operation is what is known as an “information error” which gives the user information on the operation performed. The error may be caused by the user himself or in response to other errors. If caused by the user, this error simply acts as a message in which Oracle is providing information on the query performed. Otherwise, the user must find the source of the error in order to correct it. In most cases, ORA-01013: user requested cancel of current operation should not be difficult to resolve with a few changes in Oracle settings.


The Problem

ORA-01013: user requested cancel of current operation occurs when an Oracle operation is interrupted. The following message is what you will see:

ORA -01013: user requested cancel of current operation

This may have been intentional if you decided to cancel running the code mid-operation by pressing Control+C or by some front-end application. Otherwise, it may have been caused by a timeout in a SQL pass through query. To confirm that this error is indeed a result of a timeout, you should identify which function in the BDF script is raising the error. Oracle 8 ODBC driver and SQL*Net both implement a timeout.


The Solution

If the user intentionally shut down the operation, the user simply proceeds to the next operation. If the reason for the error is timeouts, the timeout parameter should be changed to a higher value. If you set the statement timeout to -1, statements should not timeout. This should be default setting.

If you are using open database connectivity (ODBC) in Oracle, you have the option of enabling timeouts so that you do not face this error message again. To enable timeouts, go to your Control Panel and click on Administrative Tools. In the Administrative Tools dialog box, clock data sources (ODBC). Select your ODBC connection. On the configuration page, look for the box next to “Enable ODBC Timeout” and make sure that is box is unchecked. This will prevent further timeouts from occurring.


Moving Forward

If you are using ODBC, changing your timeout settings is a good way to eliminate seeing the error due to a timeout. If you are still facing this error even after taking the necessary steps outlined above, contact your database administrator. Your DBA may be able to identify the problem and help you get past the cancellation error. You may also consider consulting an Oracle professional to resolve this issue as well as meet any other needs you may have with your system. Remember to always check the consulting firm’s credentials and experience level to receive the best possible help for your specific needs.


Submit your question