ORA-01013 : user requested cancel of current operation

ORA-01013 : user requested cancel of current operation

Message : query error, ORA-01013: user requested cancel of current operation

Cause :

1. The current operation has been terminated by the user. There is no course of action to take. This message is informational only.
              If you interrupted an Oracle operation by pressing Ctrl+C or by canceling the operation through another method (i.e. front-end application).

2. This error may also have been caused by a timeout in a sql pass-through query.

Check List : 

1. Alert Log : 

WARNING: Oracle executable binary mismatch detected.
 Binary of new process does not match binary which started instance
issue alter system set "_disable_image_check" = true to disable these messages


According to the Metalink, this error is due to Oracle during startup, start the Oracle binaries change, or change the parameters or play a patch, then cause this problem. Oracle to this change is detected, suggesting that this problem ALERT file in the database. This information is just a warning, confirm the installation file operations, you can be prompted by alarm information given in this error message shielding. Grid Infrastructure software on my server does upgrade from 11.2.0.1 to 11.2.0.2 

Run the following command, the error message to be shielded from the ALERT file:

alter system set "_disable_image_check" = true scope=both;

2. Which parameter is responsible for the sqlplus connection timeout ?

\NETWOKR\ADMIN\sqlnet.ora 

contains the following entries:

SQLNET.INBOUND.CONNECT_TIMEOUT = 300
SQLNET.SEND_TIMEOUT = 300 
SQLNET.RECV_TIMEOUT = 300

3. Checked the default limit of resources from dba_profiles.

SQL> select resource_name, limit from dba_profiles where profile='DEFAULT';

RESOURCE_NAME                    LIMIT
-------------------------------- ----------------------------------------
COMPOSITE_LIMIT                  UNLIMITED
SESSIONS_PER_USER                UNLIMITED
CPU_PER_SESSION                  UNLIMITED
CPU_PER_CALL                     UNLIMITED
LOGICAL_READS_PER_SESSION        UNLIMITED
LOGICAL_READS_PER_CALL           UNLIMITED
IDLE_TIME                        UNLIMITED
CONNECT_TIME                     UNLIMITED
PRIVATE_SGA                      UNLIMITED
FAILED_LOGIN_ATTEMPTS            10
PASSWORD_LIFE_TIME               UNLIMITED

RESOURCE_NAME                    LIMIT
-------------------------------- ----------------------------------------
PASSWORD_REUSE_TIME              UNLIMITED
PASSWORD_REUSE_MAX               UNLIMITED
PASSWORD_VERIFY_FUNCTION         NULL
PASSWORD_LOCK_TIME               UNLIMITED
PASSWORD_GRACE_TIME              UNLIMITED

Here, if any parameter limit is not unlimited then please set that parameter to unlimited.

To alter a limit (e.g. to set IDLE_TIME to UNLIMITED)

alter profile default limit idle_time UNLIMITED;

SQLNET INBOUND_CONNECT_TIMEOUT is the timeout for initiating a session. When a client makes a connection to the database server but does not send authentication information (username/password) within the INBOUND_CONNECT_TIMEOUT, the connection is dropped and an error is written to the alert.log.

However, this parameter does NOT affect database sessions after they have begun -- i.e. after they have connected and authenticated successfully.

RESOLUTION :

The option(s) to resolve this Oracle error are:

Option #1

The current operation has been terminated by the user. There is no course of action to take. This message is informational only.

Option #2

This error may also have been caused by a timeout in a sql pass-through query. To resolve this error, properties of the timeout parameter need to be changed to a higher value.