How to resolve ORA-00600 [13013], [5001] [ID 816784.1]

Applies to:

Oracle Server – Enterprise Edition – Version: 10.2.0.4

Information in this document applies to any platform.

Goal

The Goal of this article is to resolve Ora-00600[13013] and check if there are any known bugs associated with this error to prevent future occurence of this issue

Solution

Section 1> What information needs to be Collected

The Second argument would give the information about the data object id.

This would give information about the object involved.

SQL>Select object_name,object_type,owner from dba_objects where data_object_id=<value reported in argment b>

Once the Object is identified run the following :

The below command check if the table has corruption or not .

SQL> Analzye table <owner>.<table name> validate structure online ;

If this goes fine table doesnot have corruption. For next command.

If the above command fails with ORA-1498 go to Section 3

The below comman check if table/index has corruption or not

SQL>Analzye table <owner>.<table name> validate structure case online ;

If the above command errors out with ora-1499 it indicates a corruption in index.

Go to section 2 for resolution

Run dbverify on the datafile reported in the error

Arg [c] in the ora-0600[13011] would give the Relative DBA

Section 2 >How to resolve if a Index is corrupted

Section 3> How to resolve if table is corrupted

Option a>  Backup is available

Ora-1498 would be reported on the table.

The trace file from Ora-1498 would contain following information

Example

Run dbverify on the datafile containing the table

dbv file=<location of datafile> blocksize=<db_block_size>

Corruption would be reported on the block.

If you have an Rman backup do a Rman block recovery (Take the file number and block number affected from the trace file)

Rman> Blockrecover datafile <no> block <block number>

Or

If you have a user managed backup you can do an restore and recovery from good copy of the problematic datafile

Option b> Backup is not available

If no backups are available then use event 10231 at session level to create a salvage table

SQL>alter session set events ’10231 trace name context forever, level 10′

SQL> Create table <owner>.salvage_table as select * from <Corrupted table> ;

Rename the Original table to old.

Rename salvage table to Original table name

or

You can use dbms_repair script to mark the block soft corrupt.

Note 556733.1

DBMS_REPAIR SCRIPT

How to resolve when Smon terminates the instance due to Ora-00600[13013]

If Smon is terminating the instance then.

Set event 10513 and startup the database

event=”10513 trace name context forever, level 2″

SQL>Startup mount ;

SQL>Show parameter event

SQL>Alter datatabase open ;

Identify the object involved using information from Section 1.

How to resolve the issue if the object involved belongs to system tablespace

System objects are very important.

Please open a Service request with Oracle support if system tables are involved.

Are there any known bugs

© 2009, www.oracledatabase12g.com. 版权所有.文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.

相关文章 | Related posts:

1. Oracle内部错误:ORA-00600[25012]一例
2. Summary of Bugs Containing ORA – 00600 [KCBNEW_3]
3. How to trigger ORA-00600,ORA-7445 by manual
4. ORA-00600 [kddummy_blkchk]错误一例
5. ORA-00600 [kcblasm_1] May Occur After Applying The Patch 7523755
6. ORA-00600 [3756]内部错误一例
7. ORA-600 [6006] ORA-600 [6856] During Startup Instance, Followed by Termination by SMON
8. Possible Cause of ORA-00354 and ORA-00353 -OR- ARC0: Error 19510 closing archivelog file
9. How to Format Corrupted Block Not Part of Any Segment
10. Troubleshooting Streams Apply Error ORA-1403, ORA-26787 or ORA-26786