How to handle mon_mod $ Table ORA-600 13013 errors in oracle

Some friends feedback database startup run after a little time, then automatic crash, let us help find the reason, through analysis is because the smon process triggers ORA-600 13013 caused database exceptions
Alert Log error message
Thu Aug 4 18:39:44 2016
Database Characterset is ZHS16GBK
Replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid = 33, OS id = 22935
Thu Aug 4 18:39:44 2016
Completed: ALTER DATABASE OPEN
Thu Aug 4 18:39:44 2016
Db_recovery_file_dest_size of 2048 MB is 0.00% used. This is
User-specified limit on the amount of space that will be used by this
Database for recovery-related files, and does not reflect the amount
Space available in the underlying filesystem or ASM diskgroup.
Thu Aug 4 18:48:41 2016
Thread 1 advanced to log sequence 86746
Current log #3 seq #86746 mem #0:/opt/ora10/oradata/ora10g/redo03.log
Thu Aug 4 18:58:13 2016
Errors in file/opt/ora10/admin/ora10g/bdump/ora10g_smon_22449.trc:
ORA-00600: internal error code, arguments: [13013], [5001], [482], [4198075], [40], [4198075], [17], []
Thu Aug 4 18:58:56 2016
Non-fatal internal error happenned while SMON was doing flushing of monitored table stats.
SMON encountered 8 out of maximum 100 non-fatal internal errors.
Thu Aug 4 18:59:06 2016
Errors in file/opt/ora10/admin/ora10g/bdump/ora10g_smon_22449.trc:
ORA-00600: internal error code, arguments: [13013], [5001], [482], [4198075], [40], [4198075], [17], []
Thu Aug 4 18:59:08 2016
Errors in file/opt/ora10/admin/ora10g/bdump/ora10g_pmon_22413.trc:
ORA-00474: SMON process terminated with error.
Thu Aug 4 18:59:08 2016
PMON: terminating instance due to error 474
Instance terminated by PMON, pid = 22413
Through the trace file, we can probably find that the database crash is caused by a ORA-600 13013 error, and there is an error message like "SMON was doing flushing of monitored table stats" here, based on experience, it is likely that smon collects information about the dml operations of the table.

ORA-600 [13013] meaning
ORA-600 [13013] [a] [B] {c} [d] [e] [f]
 
 
This format relates to Oracle Server 8.0.3 to 10.1
 
Arg [a] Passcount
Arg [B] Data Object number
Arg {c} Tablespace Relative DBA of block containing the row to be updated
Arg [d] Row Slot number
Arg [e] Relative DBA of block being updated (shocould be same as 1)
Arg [f] Code
Based on this error message and the description in How to resolve ORA-00600 [13013], [5001] [ID 816784.1]

ORA-600 13013 objects
SQL> select object_name from dba_objects where object_id = 482
 
OBJECT_NAME
--------------------------------------------------------------------------------
Mon_mod $
This object is a table related to the monitoring of dml changes. smon will perform related operations on it. I wrote an article about mon_mod $ and MON_MODS_ALL $ to count the number of DML operations.
Processing for mon_mod $ Table ORA-600 13013
SQL> analyze table mon_mod $ validate structure cascade;
 
Analyze table mon_mod $ validate structure cascade
*
ERROR at line 1:
ORA-01499: table/index cross reference failure-see trace file
 
 
SQL> select index_name from dba_indexes where table_name = 'mon _ mod $ ';
 
INDEX_NAME
------------------------------
I _mon_mod $ _ OBJ
 
SQL> alter index I _mon_mod $ _ OBJ REBUILD;
 
Index altered.
 
SQL> analyze table mon_mod $ validate structure cascade;
Analyze table mon_mod $ validate structure cascade
*
ERROR at line 1:
ORA-01499: table/index cross reference failure-see trace file
 
SQL> CREATE TABLE MON_MODS_BAK AS SELECT * FROM mon_mod $;
 
Table created.
 
SQL> SELECT COUNT (*) FROM mon_mod $;
 
COUNT (*)
----------
1247
 
SQL> C/mon_mod $/MON_MODS_BAK;
1 * select count (*) FROM MON_MODS_BAK
SQL>/
 
COUNT (*)
----------
1247
 
SQL> TRUNCATE TABLE mon_mod $;
 
Table truncated.
 
SQL> INSERT INTO mon_mod $ SELECT * fROM MON_MODS_BAK;
 
1247 rows created.
 
SQL> COMMIT;
 
Commit complete.
 
SQL> analyze table mon_mod $ validate structure cascade;
 
Table analyzed.
Since then on mon_mod $ Table-related ORA-600 13013 exception handling is complete, of course, you can also solve by rebuilding I _mon_mod $ _ OBJ index, but cannot solve through rebuild index. the database won't be crash.