可怕的ORA-600

 

 

 

Dump file /u01/app/oracle/diag/rdbms/ncrac/ncrac12/incident/incdir_107485/ncrac12_j002_706_i107485.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1
System name:    Linux
Node name:      GIO-YW18151
Release:        2.6.18-308.el5
Version:        #1 SMP Fri Jan 27 17:17:51 EST 2012
Machine:        x86_64
Instance name: ncrac12
Redo thread mounted by this instance: 2
Oracle process number: 284
Unix process pid: 706, image: oracle@GIO-YW18151 (J002)

*** 2016-07-27 22:24:07.759
*** SESSION ID:(1416.64541) 2016-07-27 22:24:07.759
*** CLIENT ID:() 2016-07-27 22:24:07.759
*** SERVICE NAME:(SYS$USERS) 2016-07-27 22:24:07.759
*** MODULE NAME:(DBMS_SCHEDULER) 2016-07-27 22:24:07.759
*** ACTION NAME:(ORA$AT_SQ_SQL_SW_19132) 2016-07-27 22:24:07.759

Dump continued from file: /u01/app/oracle/diag/rdbms/ncrac/ncrac12/trace/ncrac12_j002_706.trc
ORA-00600: internal error code, arguments: [qkaffsindex5], [], [], [], [], [], [], [], [], [], [], []

========= Dump for incident 107485 (ORA 600 [qkaffsindex5]) ========

*** 2016-07-27 22:24:07.760
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=2zburtsqfmsgk) -----

 

select sql_text,sql_fulltext from v$sql where sql_id='2zburtsqfmsgk';

/* SQL Analyze(1416,1) */ SELECT t_1.diqu diqu, t_1.codes codes, sum ( t_1.meoney / 10000 ) SUM_meoney FROM ( ( SELECT a.codes codes, sum ( b.money ) meoney, b.diqu diqu, b.xmcode xmcode, a.code code
FROM ( SELECT substr ( bd_inoutbusiclass.code, 1, 3 ) code, bd_inoutbusiclass.code codes, ( SELECT a.name name FROM bd_inoutbusiclass a WHERE a.code = substr ( bd_inoutbusiclass.code, 1, 3 ) ) nameone
, ( SELECT b.name name FROM bd_inoutbusiclass b WHERE b.code = substr ( bd_inoutbusiclass.code, 1, 5 ) ) nametwo, ( SELECT c.name name FROM bd_inoutbusiclass c WHERE c.code = substr ( bd_inoutbusiclas
s.code, 1, 7 ) ) namethree, ( decode ( length ( bd_inoutbusiclass.code ), 9, ( SELECT c.name name FROM bd_inoutbusiclass c WHERE c.code = substr ( bd_inoutbusiclass.code, 1, 9 ) ), 11, ( SELECT c.name
 name FROM bd_inoutbusiclass c WHERE c.code = substr ( bd_inoutbusiclass.code, 1, 9 ) ), NULL ) ) namefour, bd_inoutbusiclass.name xmname, bd_inoutbusiclass.pk_inoutbusiclass pk_inoutbusiclass, ( 0 )

 

 

 

 

ora-600，十有八九就是bug羅，看看oracle官方說法：

 

ORA-00600 [qkaffsindex5] from SQL Tuning Advisor Job (文檔 ID 1462688.1)

解決方法：

SOLUTION

Apply Patch 13616375 if available , No workaround exists for the bug.

This issue is fixed in :

• 12.1.0.1 (Base Release)
• 11.2.0.4 (Future Patch Set)
• 11.2.0.3.6 Database Patch Set Update
• 11.2.0.3 Bundle Patch 15 for Exadata Database
• 11.2.0.2.11 Database Patch Set Update
• 11.2.0.2 Bundle Patch 21 for Exadata Database
• 11.2.0.3 Patch 8 on Windows Platforms
• 11.2.0.2 Patch 26 on Windows Platforms

To Verify that the issue is really solved , You can wait for the next coming run of the SQL Tuning Advisor Job , which used to cause this error .

You can verify about the SQL Tuning Advisor Job , Run and completion by checking the alert log file for :

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

 

or using :

SQL> select JOB_NAME,JOB_STATUS,JOB_START_TIME,JOB_ERROR from DBA_AUTOTASK_JOB_HISTORY where CLIENT_NAME='sql tuning advisor' order by JOB_START_TIME desc;

 

 

 

bug不可怕，可怕的bug致使宕機！

固然，這個bug到不至於到時數據庫宕機，放心大吉！