ORA-16957: SQL Analyze time limit interrupt

巡查alert发现如下报错：

Wed Dec 09 22:16:37 2015

Errors in file /u01/PROD/oracle/diag/rdbms/prod/PROD1/trace/PROD1_j000_75313.trc:

ORA-16957: SQL Analyze time limit interrupt

Wed Dec 09 23:00:08 2015

End automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"

Wed Dec 09 23:00:33 2015

检查trace文件：

**************************************************************

Execution Statistics

Exec count: 1

CR gets: 67564

CU gets: 0

Disk Reads: 0

Disk Writes: 0

IO Read Requests: 0

IO Write Requests: 0

Bytes Read: 0

Bytes Written: 0

Bytes Exchanged with Storage: 0

Bytes Exchanged with Disk: 0

Bytes Simulated Read: 0

Bytes Simulated Returned: 0

Elapsed Time: 1651 (ms)

CPU Time: 1644 (ms)

User I/O Time: 0 (us)

ORA-16957: SQL Analyze time limit interrupt

*** 2015-12-09 22:16:21.267

Dump of memory from 0x00000013048D36F8 to 0x00000013048D7900

13048D36F0 53202A2F 41204C51 [/* SQL A]

13048D3700 796C616E 3128657A 30353331 2029312C [nalyze(11350,1) ]

13048D3710 57202F2A 20485449 20545454 200A5341 [*/ WITH TTT AS. ]

13048D3720 4C455328 20544345 5F502E54 58524B53 [(SELECT T.P_SKRX]

......

......

......

......

13048D78B0 44494550 20200A2C 20202020 20202020 [PEID,. ]

13048D78C0 20202020 20202020 20202020 45532820 [ (SE]

13048D78D0 5443454C 2E4E5020 49544E45 4E5F5954 [LECT PN.ENTITY_N]

13048D78E0 0A454D41 20202020 20202020 20202020 [AME. ]

13048D78F0 20202020 20202020 20202020 52462020 [ FR]

*** 2015-12-09 22:16:50.895

status=(pst=TIMEOUT)

**************************************************************

貌似没啥发现

还是去看看官网说法吧

Troubleshooting: ORA-16957: "SQL Analyze time limit interrupt" Errors (文档 ID 1275248.1)

转到底部

In this Document Symptoms Cause Solution References APPLIES TO: Oracle Database - Enterprise Edition - Version 11.1.0.6 and later Information in this document applies to any platform. SYMPTOMS The following error is reported in the alert.log: ORA-16957: SQL Analyze time limit interrupt CAUSE The ORA-16957 error is an internal error code used to indicate that SQL Tuning Task has reached the time limit for tuning a specific sql. The default time limit is 1800 seconds. SOLUTION 1.Check the current timing: COLUMN parameter_value FORMAT A30 SELECT parameter_name, parameter_value FROM dba_advisor_parameters WHERE task_name = 'SYS_AUTO_SQL_TUNING_TASK' AND parameter_name IN ('TIME_LIMIT', 'DEFAULT_EXECUTION_TYPE', 'LOCAL_TIME_LIMIT'); Then, increase the time: BEGIN DBMS_SQLTUNE.SET_TUNING_TASK_PARAMETER(task_name => 'SYS_AUTO_SQL_TUNING_TASK', parameter => 'TIME_LIMIT', value => 7200); END; 2. ORA-16957 may appear in the alert.log together with other error messages or alone: Together with other errors: Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x2B3533343949] [PC:0x22F0025, kxsffir()+337] [flags: 0x0, count: 1] Errors in file /diag/rdbms/orcl/trace/ORCL_j000_32621.trc (incident=353044): ORA-07445: exception encountered: core dump [kxsffir()+337] [SIGSEGV] [ADDR:0x2B3533343949] [PC:0x22F0025] [Address not mapped to object] [] ORA-16957: SQL Analyze time limit interrupt Incident details in: /diag/rdbms/orcl/ORCL/incident/incdir_353044/ORCL_j000_32621_i353044. In this case, investigate the underlying error that resulted in the Tuning Task timing out The error appears without reference to other errors: When the error appears in the alert.log alone, you need to investigate the SQL that is hitting the time limit in order to understand whether the timeout is legitmate or not: Is the SQL indeed large and complex and should it take 30 minutes to analyze? In order to obtain more information on the relevant SQL, check the trace file indicated with the ORA-16957 error in the alert.log Setting the following event may provide more information in the trace file: alter system set events '16957 trace name ERRORSTACK level 3'; Once the error occurs and a trace file is created disable the event as follows: alter system set events '16957 trace name context off'; REFERENCES