ora-600ang ora-7445同时发生
11月30日到12月1日间，一个11.2.0.3 RAC环境的alert日志中发现大量的at Nov 30 18:07:22 2013
Begin automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Exception
Errors in file /opt/oracle/diag/rdbms/clarity/clarity1/trace/clarity1_j001_13899.trc (incident=718490):
ORA-07445: exception encountered: core dump []
Incident details in: /opt/oracle/diag/rdbms/clarity/clarity1/incident/incdir_718490/clarity1_j001_13899_i718490.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /opt/oracle/diag/rdbms/clarity/clarity1/trace/clarity1_j001_13899.trc (incident=718491):
ORA-00600: internal error code, arguments: , , [], [], [], [], [], [], [], [], [], []
ORA-07445: exception encountered: core dump []
Incident details in: /opt/oracle/diag/rdbms/clarity/clarity1/incident/incdir_718491/clarity1_j001_13899_i718491.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /opt/oracle/diag/rdbms/clarity/clarity1/incident/incdir_718490/clarity1_j001_13899_i718490.trc:
ORA-00600: internal error code, arguments: , , [], [], [], [], [], [], [], [], [], []
ORA-07445: exception encountered: core dump []
不知道是什么原因，但库的运行上没有发现什么异常之处。 *** 2013-11-30 18:07:28.669
*** SESSION ID:(1154.217) 2013-11-30 18:07:28.669
*** CLIENT ID:() 2013-11-30 18:07:28.669
*** SERVICE NAME:(SYS$USERS) 2013-11-30 18:07:28.669
*** MODULE NAME:(DBMS_SCHEDULER) 2013-11-30 18:07:28.669
*** ACTION NAME:(ORA$AT_SQ_SQL_SW_1326) 2013-11-30 18:07:28.669
Dump continued from file: /opt/oracle/diag/rdbms/clarity/clarity1/trace/clarity1_j001_13899.trc
ORA-00600: internal error code, arguments: , , [], [], [], [], [], [], [], [], [], []
ORA-07445: exception encountered: core dump []
*** 2013-11-30 18:07:28.744
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x40)
----- Current SQL Statement for this session (sql_id=6607p8k3qdrpp) -----
SELECT NAME FROM ODF_AUD_LOOKUP_CAPTIONS WHERE ID= :B2 AND LANGUAGE_CODE=:B1
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0x15e8cc7c0 17 function NIKU.ODF_AUD_VALUE_FCT
0x15c52bfe0 1 anonymous block
0x15c8c6b78 11816 package body SYS.DBMS_SQLTUNE_INTERNAL
0x15bb9d560 7 SYS.WRI$_ADV_SQLTUNE
0x15c957950 587 package body SYS.PRVT_ADVISOR
0x15c957950 2655 package body SYS.PRVT_ADVISOR
0x15d61b280 241 package body SYS.DBMS_ADVISOR
0x134ca96a8 821 package body SYS.DBMS_SQLTUNE
0x15d5ea360 4 anonymous block Bug 16719520 : ORA-600 EXECUTING SELECT
Product Version 11.2.0.3
Hdr: 16719520 11.2.0.3 RDBMS 11.2.0.3 SQL EXECUTION PRODID-5 PORTID-226 ORA-600
Abstract: ORA-600 EXECUTING SELECT
BUG TYPE CHOSEN
===============
Code
== SubComponent: Memory Management ==
=====================================
DETAILED PROBLEM DESCRIPTION
============================
Excuting select SQL statement causes ORA-600 and
ORA-7445
.
It is a large SQL statement that beyond 350 lines and the details was output
into the incident file isdb_ora_10390_i576355.trc. When the outer section of
SQL statement "select count (*) " was removed , the error can be avoided.
Customer can reproduce the BUG 100%. And I can't test it due to too many
objects
and data related.
DIAGNOSTIC ANALYSIS
===================
One parameter of ORA-7445 is SI_KERNEL(general_protection). It seems that
some memory was locked. DBMS_SCHEDULER调度了 ORA$AT_SQ_SQL_SW_1326， 可以通过禁用自动sql tuning task来绕过该问题
BEGIN
dbms_auto_task_admin.disable(
client_name => 'sql tuning advisor',
operation => NULL,
window_name => NULL);
END;
/ 谢谢，刘大。 我也找了一下MOS，感觉下面几个错误也有可能。如果方便请刘大确认一下。
Bug 14680506 Memory corruption / ORA-7445 / ORA-600 from domain index on ADT column
Bug 14102873 Memory corruption from function based index / virtual column in SORT AGGREGATE in PQ
Bug 16268425 Memory corruption / ORA-7445 / ORA-600 gathering statistics in parallel for table with virtual column/s
注意你列的几个 Note的描述和你的问题本质有哪一个是吻合的？ 相信ML，专业售后，确认bug都有流程和匹配规范的，不是看字面报错的，O(∩_∩)O哈哈~ 谢谢，刘大的指点
页:
[1]