<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>《ORA-600[6749] 发生在 SYSMAN.MGMT_METRICS_RAW表》的评论</title>
	<atom:link href="https://www.xifenfei.com/2012/06/ora-6006749-%e5%8f%91%e7%94%9f%e5%9c%a8-sysman-mgmt_metrics_raw%e8%a1%a8.html/feed" rel="self" type="application/rss+xml" />
	<link>https://www.xifenfei.com/2012/06/ora-6006749-%e5%8f%91%e7%94%9f%e5%9c%a8-sysman-mgmt_metrics_raw%e8%a1%a8.html</link>
	<description>提供7*24专业数据库(Oracle,SQL Server,MySQL,PostgreSQL等)恢复和技术支持@Tel:17813235971</description>
	<lastBuildDate>Thu, 11 Dec 2025 02:46:14 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>作者：惜分飞</title>
		<link>https://www.xifenfei.com/2012/06/ora-6006749-%e5%8f%91%e7%94%9f%e5%9c%a8-sysman-mgmt_metrics_raw%e8%a1%a8.html/comment-page-1#comment-935</link>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
		<pubDate>Wed, 25 Jul 2012 14:59:05 +0000</pubDate>
		<guid isPermaLink="false">https://www.xifenfei.com/?p=3295#comment-935</guid>
		<description><![CDATA[&lt;blockquote cite=&quot;comment-934&quot;&gt;


select * from dba_extents where 3056 between block_id and block_id + blocks and file_id=3;
这里的3056是什么，应该是dba吧，是不是写错了，你这案例的dba应该是13970 吧！


&lt;/blockquote&gt;
谢谢,确实在写blog时出现失误,已经更正]]></description>
		<content:encoded><![CDATA[<blockquote cite="comment-934">
<p>select * from dba_extents where 3056 between block_id and block_id + blocks and file_id=3;<br />
这里的3056是什么，应该是dba吧，是不是写错了，你这案例的dba应该是13970 吧！</p>
</blockquote>
<p>谢谢,确实在写blog时出现失误,已经更正</p>
]]></content:encoded>
	</item>
	<item>
		<title>作者：xingjian</title>
		<link>https://www.xifenfei.com/2012/06/ora-6006749-%e5%8f%91%e7%94%9f%e5%9c%a8-sysman-mgmt_metrics_raw%e8%a1%a8.html/comment-page-1#comment-934</link>
		<dc:creator><![CDATA[xingjian]]></dc:creator>
		<pubDate>Wed, 25 Jul 2012 11:22:39 +0000</pubDate>
		<guid isPermaLink="false">https://www.xifenfei.com/?p=3295#comment-934</guid>
		<description><![CDATA[select * from dba_extents where 3056 between block_id and block_id + blocks and file_id=3;
这里的3056是什么，应该是dba吧，是不是写错了，你这案例的dba应该是13970 吧！]]></description>
		<content:encoded><![CDATA[<p>select * from dba_extents where 3056 between block_id and block_id + blocks and file_id=3;<br />
这里的3056是什么，应该是dba吧，是不是写错了，你这案例的dba应该是13970 吧！</p>
]]></content:encoded>
	</item>
	<item>
		<title>作者：惜分飞</title>
		<link>https://www.xifenfei.com/2012/06/ora-6006749-%e5%8f%91%e7%94%9f%e5%9c%a8-sysman-mgmt_metrics_raw%e8%a1%a8.html/comment-page-1#comment-866</link>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
		<pubDate>Thu, 07 Jun 2012 06:09:11 +0000</pubDate>
		<guid isPermaLink="false">https://www.xifenfei.com/?p=3295#comment-866</guid>
		<description><![CDATA[ORA-600 [6749] Occurring on SYSMAN.MGMT_METRICS_RAW
[shell]
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 &#039;/u04/oradata/ACCESS16/ataccess/redo4.log&#039; 
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=&#039;ATACCESS&#039; 
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 &#039;%IOT%&#039;;  

.  
..  
...  

SYS_IOT_OVER_49766 AQ$_MGMT_NOTIFY_QTABLE_G  
SYS_IOT_OVER_49869 MGMT_METRICS_RAW  &lt;&lt;&lt;&lt;&lt;&lt;&lt;------------
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&gt; create table SYSMAN.MGMT_METRICS_RAW_COPY 
as select * from SYSMAN.MGMT_METRICS_RAW;

3. Truncate the table:

SQL&gt; truncate table SYSMAN.MGMT_METRICS_RAW;

May need  to disable trigger: &quot;sysman.raw_metrics_after_insert&quot; before proceeding.  
Re-enable after the insert.

4. Re-insert the rows:

SQL&gt; insert into SYSMAN.MGMT_METRICS_RAW 
select * from SYSMAN.MGMT_METRICS_RAW_COPY; 
SQL&gt; commit;

5. Drop the copy table:

SQL&gt; drop table SYSMAN.MGMT_METRICS_RAW_COPY; 
[/shell]]]></description>
		<content:encoded><![CDATA[<p>ORA-600 [6749] Occurring on SYSMAN.MGMT_METRICS_RAW</p>
<pre class="brush: bash; title: ; notranslate">
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  &lt;&lt;&lt;&lt;&lt;&lt;&lt;------------
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&gt; create table SYSMAN.MGMT_METRICS_RAW_COPY 
as select * from SYSMAN.MGMT_METRICS_RAW;

3. Truncate the table:

SQL&gt; truncate table SYSMAN.MGMT_METRICS_RAW;

May need  to disable trigger: &quot;sysman.raw_metrics_after_insert&quot; before proceeding.  
Re-enable after the insert.

4. Re-insert the rows:

SQL&gt; insert into SYSMAN.MGMT_METRICS_RAW 
select * from SYSMAN.MGMT_METRICS_RAW_COPY; 
SQL&gt; commit;

5. Drop the copy table:

SQL&gt; drop table SYSMAN.MGMT_METRICS_RAW_COPY; 
</pre>
]]></content:encoded>
	</item>
</channel>
</rss>
