My Oracle Support Banner

ORA-600 [5463] While SMON is Doing Temporary Segment Drop (Doc ID 422039.1)

Last updated on FEBRUARY 12, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.1 to 12.1.0.2 [Release 9.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Checked for relevance on 01-Nov-2010


Symptoms

When starting the database after a crash or for normal maintenance after a truncate table, the error below will occur 100 times and then the instance will crash. 

The errors are caused because SMON is trying to clean a temp segment in a tablespace by looking at the bitmap index in the tablespace.  The bitmap index is corrupted and this causes SMON to fail when trying to clean up the segment.

From the alert.log:

ORA-00600: internal error code, arguments: [5463], [], [], [], [], [], [], []
Non-fatal internal error happenned while SMON was doing temporary segment drop.
SMON encountered 53 out of maximum 100 non-fatal internal errors.

Changes

The issue occurred after a table was truncated with drop storage option.

ORA-00600: internal error code, arguments: [5463], [], [], [], [], [], [], []
Current SQL statement for this session:

TRUNCATE TABLE <TABLE_NAME> DROP STORAGE

Another possible error which can be encountered is:

ORA-00600: internal error code, arguments: [ktecgeb-2], [1], [0], [], [], [], [], [], [], [], [], []

Cause

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
Symptoms
Changes
Cause
Solution
References

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