My Oracle Support Banner

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

Last updated on FEBRUARY 01, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.0 [Release 10.1 to 11.2]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
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

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 Section 1> What information needs to be Collected
 Section 2 >How to resolve if a Index is corrupted
 Section 3> How to resolve if table is corrupted
 How to resolve when SMON terminates the instance due to ORA-00600 [13013]
 How to resolve the issue if the object involved belongs to system tablespace
 Identifying the row having issue when the table is having corruption.
 Are there any Known Bug
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.