Modified:13-Jun-2013Type:PROBLEM Rate this document Email link to this document Open document in new window Printable Page
In this Document
Symptoms
Cause
Solution
References
--------------------------------------------------------------------------------
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;
References
BUG:6127434 - ORA-600[6749] RAISED BY DELETE COMMAND; NO CORRUPTION IDENTIFIED
#############################################