ORA-16957: SQL Analyze Time Limit Interrupt While Running Optimizer Statistics Collection
(Doc ID 2460391.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Information in this document applies to any platform.
Symptoms
- Error 'ORA-16957: SQL Analyze time limit interrupt' is found in alert log and OEM
- Time limit for Auto SQL Tuning Advisor job is set higher then the default as described in Doc ID 1275248.1
- Trace for the error shows that the statement picked up is part of stats collection job and looks like :
/* SQL Analyze(..) */ select client_name, job_status, to_char(job_start_time,'DD-MON-YYYY HH:MI:SS') as JobStart from DBA_AUTOTASK_JOB_HISTORY where job_start_time > sysdate -5
- AWR shows DBMS_STATS is running at the same time :
Elapsed Time (s) Executions Elapsed Time per Exec (s) %Total %CPU %IO SQL Id SQL Module SQL Text
605.70 1 605.70 71.67 99.35 0.54 5zruc4v6y32f9 DBMS_SCHEDULER DECLARE job BINARY_INTEGER := ...
369.17 14 26.37 43.68 98.97 0.85 0xy7sm48tx78v DBMS_SCHEDULER /* SQL Analyze(238, 1) */ sele... <<
59.42 1 59.42 7.03 94.21 1.24 b6usrg82hwsa3 DBMS_SCHEDULER call dbms_stats.gather_databas... <<
Changes
No particular change
Cause
| |
To view full details, sign in with your My Oracle Support account. |
|
| Don't have a My Oracle Support account? Click to get started! |
In this Document
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.