Ora 01013 описание ошибки

oracle tutorial webinars

ORA-01013

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.

What could be the reason and prerequisites for Error: ORA-01013 user requested cancel of current operation?

Instead of waiting for the completion, Oracle provides the option to cancel running SQL statements. If a running statement is terminated, an ORA-01013 return code is issued by the Oracle. This return code is an information or confirmation message and is not an error.

The error is not logged in the system log or as a short dump by the database interface. There is a technically unavoidable exception while the system is processing a recursive statement if an error ORA-01013 is triggered and by an error ORA-00604, the error ORA-01013 is consequently preceded. In this situation, ORA-00604 is only recognized by the database interface which may be more or less critical, depending on the subsequent error, and in the system log the error is logged or as short dump.

In the SAP environment a termination may occur with an ORA-01013 error due to various reasons:

1. A tool with CTRL-C might have been stopped;
2. With «Stop transaction», a transaction might have been stopped explicitly.
3. Due to rdisp/max_wprun_time, a SAP timeout may occur.
4. 0 may be lower than Oracle <= 8.0.6: SQLNET.EXPIRE_TIME.

How can I get this issue fixed?

1. If the explicit or implicit execution of an SQL statement in tools are terminated such as SVRMGRL, SQLPLUS, SAPDBA, BRBACKUP, BRARCHIVE, BRCONNECT, BRRESTORE or BRRECOVER with CTRL+C, an ORA-01013 error is logged by the system logs. This is not an error and this behavior is normal.

2. In current R/3 Releases, in the upper left corner of the window a running transaction with the «Stop transaction» menu option can be terminated. A «Cancel» command is then send command to the Oracle session with this mechanism which with an ORA-01013 error then terminates. Therefore, if an ORA-01013 error has been logged by the system, the circumstances of the termination should be asked to the relevant user to determine if the message was triggered by another event or if the user has canceled the transaction intentionally.

3. In the SAP environment based on the rdisp/max_wprun_time parameter, if a timeout is triggered, a «Cancel» command is send by the R/3 system to the database session that triggers an error ORA-01013. Therefore, it is essential to check in connection with the ORA-01013 whether lengthy SELECTs have occurred. In the trace of the affected work process, the lengthy statement will also be logged, where necessary. The long-running program should be optimized.

Network problems are the most likely cause if the problem cannot be reproduced.

1. In the sqlnet.ora file a period (in minutes) can be specified with the Oracle Net SQLNET.EXPIRE_TIME parameter, after which automatically an inactive link (for example, following a network problem) is closed. This parameter is set to 0 (that is, it is inactive) in the SAP standard system. As a side effect, a long-lasting but still active session may be terminated with an ORA-01013 error if the parameter is set to a value higher than 0. SQLNET.EXPIRE_TIME should be reset to 0.

Проблемы

«Ошибка S1T00 Oracle ODBC ORA ORA-01013-пользователь запрашивает отмену текущей операции» Эта ошибка возникает при формировании отчета.

Причина

Параметр в источнике данных Oracle настроен неправильно.

Решение

Проверьте конфигурацию драйвера Oracle ODBC для источника данных. Снимите флажок Включить время ожидания запроса.

Ссылки

Нужна дополнительная помощь?

Нужны дополнительные параметры?

Изучите преимущества подписки, просмотрите учебные курсы, узнайте, как защитить свое устройство и т. д.

В сообществах можно задавать вопросы и отвечать на них, отправлять отзывы и консультироваться с экспертами разных профилей.

Following OEM alerts are received from databases of 11R2 to 12R2:

...
..
.
Target name=RACTEST
Incident creation time=28/11/2017 9:48:17 PM AEDT 
Last updated time=28/11/2017 9:48:17 PM AEDT 
Message= ORA-01013: user requested cancel of current operation 
Severity=Critical 
Incident ID=294770 
...
..
.

CAUSES

SQL ID 4d43by1zzjfna runs slowly until failed with ‘ORA-01013’ error.

SOLUTION

As per “low Performance Oracle Enterprise Manager SQL Metrics SQL statement (SQL ID: 4d43by1zzjfna) Automatically Run (Doc ID 2266608.1)”, the fololowing actions are taken :

(a) Stopping EM agent monitoring the RAC instance(s).

$AGENT_HOME/bin/emctl stop agent

(b) Test the current execution time ( 36 s ),  and record the execution plan via SQL PLUS:

SQL> set timing on
SQL> set autotrace on
SQL> WITH last_run AS
 (
 SELECT all_runs.OWNER ,
 all_runs.JOB_NAME,
 all_runs.STATUS
 FROM DBA_SCHEDULER_JOB_RUN_DETAILS all_runs,
 (
 SELECT OWNER ,
 JOB_NAME,
 MAX(ACTUAL_START_DATE) AS START_DATE
 FROM DBA_SCHEDULER_JOB_RUN_DETAILS
 GROUP BY OWNER,
 JOB_NAME
 )
 latest_runs
 WHERE all_runs.OWNER = latest_runs.OWNER
 AND all_runs.JOB_NAME = latest_runs.JOB_NAME
 AND all_runs.ACTUAL_START_DATE=latest_runs.START_DATE
...
..
.

SUM(BROKEN) SUM(FAILED)
----------- -----------
 0          0

Elapsed: 00:00:36.49

Execution Plan
----------------------------------------------------------
Plan hash value: 204035645
...
..
.
Statistics
----------------------------------------------------------
 338   recursive calls
 0     db block gets
 58842 consistent gets
 0     physical reads
 0     redo size
 603   bytes sent via SQL*Net to client
 524   bytes received via SQL*Net from client
 2     SQL*Net roundtrips to/from client
 8671  sorts (memory)
 0     sorts (disk)
 1 rows processed

c)Purge any job history that is no longer needed to reduce the size of job related tables:

SQL> exec DBMS_SCHEDULER.PURGE_LOG(7,which_log=>'JOB_LOG');

PL/SQL procedure successfully completed.
Elapsed: 00:00:04.95

SQL> exec DBMS_SCHEDULER.PURGE_LOG(7,which_log=>'WINDOW_LOG');

PL/SQL procedure successfully completed.
Elapsed: 00:00:00.03

SQL> exec DBMS_SCHEDULER.PURGE_LOG(log_history => 7, job_name => 'job1, sys.class2');

PL/SQL procedure successfully completed.
Elapsed: 00:00:00.04

SQL> exec DBMS_SCHEDULER.SET_SCHEDULER_ATTRIBUTE('log_history','7');

PL/SQL procedure successfully completed.
Elapsed: 00:00:00.02

d) Regather statistics to ensure that the CBO has the right understanding of cardinality/cost for execution plans involving JOB related tables:

SQL> EXEC DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;

PL/SQL procedure successfully completed.
Elapsed: 00:01:26.37

SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;

PL/SQL procedure successfully completed.
Elapsed: 00:01:35.82

SQL> EXEC DBMS_STATS.GATHER_SCHEMA_STATS ('SYS');

PL/SQL procedure successfully completed.
Elapsed: 00:10:53.24

e) rerun the same sql_id=’4d43by1zzjfna’. We can see there is a new execution plan. The running time is shorted from 36 seconds from 1 second.

SQL> WITH last_run AS
 2 (
 3 SELECT all_runs.OWNER ,
 4 all_runs.JOB_NAME,
 5 all_runs.STATUS
 6 FROM DBA_SCHEDULER_JOB_RUN_DETAILS all_runs,
 7 (
 8 SELECT OWNER ,
 9 JOB_NAME,
 10 MAX(ACTUAL_START_DATE) AS START_DATE
 11 FROM DBA_SCHEDULER_JOB_RUN_DETAILS
 12 GROUP BY OWNER,
 13 JOB_NAME
 14 )
 15 latest_runs
 16 WHERE all_runs.OWNER = latest_runs.OWNER
 17 AND all_runs.JOB_NAME = latest_runs.JOB_NAME
 18 AND all_runs.ACTUAL_START_DATE=latest_runs.START_DATE
 19 )
 20 SELECT SUM(broken),
 21 SUM(failed)
 22 FROM
 23 (
 24 SELECT DECODE(broken, 'N', 0, 1) broken,
 25 DECODE(NVL(failures,0), 0, 0, 1) failed
 26 FROM dba_jobs
 27 UNION ALL
 28 SELECT DECODE(STATE,'BROKEN',1,0) broken,
 29 DECODE(STATUS ,'FAILED',DECODE(STATE,'BROKEN',0,'DISABLED',0,1),0) failed
 30 FROM
 31 (
 32 SELECT all_jobs.OWNER ,
 33 all_jobs.JOB_NAME,
 34 last_run.STATUS ,
 35 all_jobs.STATE
 36 FROM last_run,
 37 DBA_SCHEDULER_JOBS all_jobs
 38 WHERE last_run.OWNER =all_jobs.OWNER
 39 AND last_run.JOB_NAME=all_jobs.JOB_NAME
 40 )
 41 )
 42 /

SUM(BROKEN) SUM(FAILED)
----------- -----------
 0           0

Elapsed: 00:00:01.00

Execution Plan
----------------------------------------------------------
Plan hash value: 2148836375
...
..
.
Statistics
----------------------------------------------------------
 50   recursive calls
 0    db block gets
 3585 consistent gets
 0    physical reads
 0    redo size
 603  bytes sent via SQL*Net to client
 524  bytes received via SQL*Net from client
 2    SQL*Net roundtrips to/from client
 51   sorts (memory)
 0    sorts (disk)
 1 rows processed

(f) Re-enable EM Agents monitoring the RAC instance(s):

$AGENT_HOME/bin/emctl start agent

Problem

Error

Error #-9
DMS-E-GENERAL, A general exception had occurred during operation
‘fetch’.
ORA-01013 User requested cancel of current operation.

when running a report against Oracle.

Resolving The Problem

From the Oracle Error message help file:

ORA-01013: user requested cancel of current operation

Cause: The user interrupted an Oracle operation by entering , ControlC, or another canceling operation. This forces the current operation to end. This is an informational message only.
Action: Continue with the next operation. end of processing

This error may be due to an internal Sql*Net parameter which times out
the connection. This is called sqlnet.expired.time which logs out users after a set time. Contact your DBA to reset this parameter and retry.

[{«Product»:{«code»:»SSTQPQ»,»label»:»IBM Cognos Series 7 PowerPlay»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud & Data Platform»},»Component»:»Impromptu»,»Platform»:[{«code»:»PF025″,»label»:»Platform Independent»}],»Version»:»Impromptu 2.0;Impromptu 3.03;Impromptu 3.04;Impromptu 3.5″,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]

Понравилась статья? Поделить с друзьями:
  • Ora 01012 not logged on ошибка
  • Ose exe ошибка
  • Osd ошибка на приставке lumax
  • Osconflib dll ошибка
  • Oscar editor x7 ошибка line 0