ORA-600[6749] 发生在 SYSMAN.MGMT_METRICS_RAW表

发表于 2012 年 6 月 7 日 由 惜分飞

联系：手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

标题：ORA-600[6749] 发生在 SYSMAN.MGMT_METRICS_RAW表

作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

数据库alert日志长时间出现ORA-00600[6749]错误
日志报错如下

Fri Jun  1 12:01:30 2012
Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_396.trc:
ORA-00600: internal error code, arguments: [6749], [3], [12596882], [49], [], [], [], []
Fri Jun  1 12:01:34 2012
Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_396.trc:
Fri Jun  1 13:01:06 2012
Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_13226.trc:
ORA-00600: internal error code, arguments: [6749], [3], [12596882], [49], [], [], [], []
Fri Jun  1 13:01:10 2012
Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_13226.trc:
Fri Jun  1 14:01:46 2012
Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_26691.trc:
ORA-00600: internal error code, arguments: [6749], [3], [12596882], [49], [], [], [], []
Fri Jun  1 14:01:51 2012
Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_26691.trc:
Fri Jun  1 15:01:21 2012
Errors in file /opt/oracle/admin/oraapp/bdump/oraapp_j000_7119.trc:
ORA-00600: internal error code, arguments: [6749], [3], [12596882], [49], [], [], [], []

查看trace日志

Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /opt/oracle/product/10/oraapp
System name:	Linux
Node name:	oracle2
Release:	2.6.18-92.el5
Version:	#1 SMP Tue Apr 29 13:16:15 EDT 2008
Machine:	x86_64
Instance name: oraapp
Redo thread mounted by this instance: 1
Oracle process number: 44
Unix process pid: 26691, image: oracle@oracle2 (J000)

*** ACTION NAME:(target 5) 2012-06-01 14:01:00.298
*** MODULE NAME:(Oracle Enterprise Manager.rollup) 2012-06-01 14:01:00.298
*** SERVICE NAME:(SYS$USERS) 2012-06-01 14:01:00.298
*** SESSION ID:(406.24103) 2012-06-01 14:01:00.298
Dumping current redo log in thread 1

DUMP OF REDO FROM FILE '/opt/oracle/oradata/oraapp/systable/redo03.log'
 Opcodes 11.*
 DBAs (file#, block#):
      (3, 13970)
 RBAs: 0x000000.00000000.0000 thru 0xffffffff.ffffffff.ffff
 SCNs: scn: 0x0000.00000000 thru scn: 0xffff.ffffffff
 Times: creation thru eternity
 FILE HEADER:
	Compatibility Vsn = 169869568=0xa200100
	Db ID=1462349529=0x5729aed9, Db Name='ORAAPP'
	Activation ID=1462334681=0x572974d9
	Control Seq=2614156=0x27e38c, File size=245760=0x3c000
	File Number=3, Blksiz=512, File Type=2 LOG
 descrip:"Thread 0001, Seq# 0000003963, SCN 0x0000129fc9df-0xffffffffffff"

猜测ORA-600[6749]部分参数

SQL> select  DBMS_UTILITY.data_block_address_file (12596882) "file#",
  2  DBMS_UTILITY.data_block_address_block (12596882) "block#" 
  3  from dual;

     file#     block#
---------- ----------
         3      13970

ORA-600[6749][a][b]{c}
这里证明c表示rdba

根据dba查询对象

SQL> select * from dba_extents where 13970 between block_id and block_id + blocks and file_id=3;

OWNER      SEGMENT_NAME                     SEGMENT_TYPE   
---------- ------------------------------- -------------------
SYSMAN        SYS_IOT_OVER_10448                 TABLE         

SQL> select owner,iot_name from dba_tables where table_name = 'SYS_IOT_OVER_10448';

OWNER                          IOT_NAME
------------------------------ ------------------------------
SYSMAN                         MGMT_METRICS_RAW

SQL>  ANALYZE TABLE SYSMAN.MGMT_METRICS_RAW  VALIDATE STRUCTURE CASCADE;

Table analyzed.

按照常理ORA-00600[6749]错误是因为坏块或者表和索引数据不一致导致,通过ANALYZE可以检查出来.这里显示正常,那可能是其他原因导致,查询MOS果然发现是ORA-600 [6749] Occurring on SYSMAN.MGMT_METRICS_RAW [ID 467439.1]

解决方法

The following workaround may resolve the problem temporarily:

1. Ensure you have a good backup before proceeding.

2. Create a copy of the SYSMAN.MGMT_METRICS_RAW table:

SQL> create table SYSMAN.MGMT_METRICS_RAW_COPY 
as select * from SYSMAN.MGMT_METRICS_RAW;

3. Truncate the table:

SQL> truncate table SYSMAN.MGMT_METRICS_RAW;

May need  to disable trigger: "sysman.raw_metrics_after_insert" before proceeding.  
Re-enable after the insert.

4. Re-insert the rows:

SQL> insert into SYSMAN.MGMT_METRICS_RAW 
select * from SYSMAN.MGMT_METRICS_RAW_COPY; 
SQL> commit;

5. Drop the copy table:

SQL> drop table SYSMAN.MGMT_METRICS_RAW_COPY;
此条目发表在 ORA-xxxxx 分类目录，贴了 , 标签。将固定链接加入收藏夹。

《ORA-600[6749] 发生在 SYSMAN.MGMT_METRICS_RAW表》有 3 条评论

  1. 惜分飞 说：
    2012 年 7 月 25 日22:59

    select * from dba_extents where 3056 between block_id and block_id + blocks and file_id=3;
    这里的3056是什么，应该是dba吧，是不是写错了，你这案例的dba应该是13970 吧！

    谢谢,确实在写blog时出现失误,已经更正

  2. xingjian 说：
    2012 年 7 月 25 日19:22

    select * from dba_extents where 3056 between block_id and block_id + blocks and file_id=3;
    这里的3056是什么，应该是dba吧，是不是写错了，你这案例的dba应该是13970 吧！

  3. 惜分飞 说：
    2012 年 6 月 7 日14:09

    ORA-600 [6749] Occurring on SYSMAN.MGMT_METRICS_RAW

    Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.3 and later[Release: 10.2 and later ]
Information in this document applies to any platform.
***Checked for relevance on 28-Feb-2012***

Symptoms
1. The following error is occurring in the alert.log:

ORA-00600: internal error code, arguments: [6749], [6], [12605862], [78], [], [], [], []

2. The trace file may report the DBA and block number for the error. 
If it does not, please engage Oracle Support for assistance:

TRACE FILE ataccess_j000_8790.trc 
-------------------------------------------------------- 
*** SESSION ID:(133.1713) 2007-11-02 16:00:45.275 
Dumping current redo log in thread 1 

DUMP OF REDO FROM FILE '/u04/oradata/ACCESS16/ataccess/redo4.log' 
Opcodes 11.* 
DBAs (file#, block#): (3, 22950) 
RBAs: 0x000000.00000000.0000 thru 0xffffffff.ffffffff.ffff 
SCNs: scn: 0x0000.00000000 thru scn: 0xffff.ffffffff 
Times: creation thru eternity 
FILE HEADER: 
Compatibility Vsn = 169869568=0xa200100 
Db ID=1655231844=0x62a8d564, Db Name='ATACCESS' 
Activation ID=1655191140=0x62a83664 
Control Seq=4582=0x11e6, File size=204800=0x32000 
File Number=4, Blksiz=512, File Type=2 LOG 
3. The table affected is SYSMAN.MGMT_METRICS_RAW:

SELECT tablespace_name, segment_type, owner, segment_name  
    FROM dba_extents  
    WHERE file_id = 3  
    and 22950 between block_id AND block_id + blocks - 1;  

TABLESPACE_NAME  SEGMENT_TYPE OWNER SEGMENT_NAME  
---------------  ------------ ----- ------------  
SYSAUX            TABLE       SYSMAN SYS_IOT_OVER_49869  


select table_name, iot_name from all_tables where table_name like '%IOT%';  

.  
..  
...  

SYS_IOT_OVER_49766 AQ$_MGMT_NOTIFY_QTABLE_G  
SYS_IOT_OVER_49869 MGMT_METRICS_RAW  <<<<<<<------------
SYS_IOT_OVER_49872 MGMT_CURRENT_METRICS  


Cause

This issue was investigated in Bug 6127434 but not resolved due to lack of information.

Abstract: ORA-600[6749] RAISED BY DELETE COMMAND; NO CORRUPTION IDENTIFIED 

Solution

The following workaround may resolve the problem temporarily:

1. Ensure you have a good backup before proceeding.

2. Create a copy of the SYSMAN.MGMT_METRICS_RAW table:

SQL> create table SYSMAN.MGMT_METRICS_RAW_COPY 
as select * from SYSMAN.MGMT_METRICS_RAW;

3. Truncate the table:

SQL> truncate table SYSMAN.MGMT_METRICS_RAW;

May need  to disable trigger: "sysman.raw_metrics_after_insert" before proceeding.  
Re-enable after the insert.

4. Re-insert the rows:

SQL> insert into SYSMAN.MGMT_METRICS_RAW 
select * from SYSMAN.MGMT_METRICS_RAW_COPY; 
SQL> commit;

5. Drop the copy table:

SQL> drop table SYSMAN.MGMT_METRICS_RAW_COPY;