My Oracle Support Banner

Instance Crashing With Ora-600 [15789] And Ora-474 (Doc ID 1094645.1)

Last updated on FEBRUARY 02, 2022

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.4 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product.  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner. 

User-specified limit on the amount of space that will be used by this.

Mon May 3 18:58:40 2010
Fatal internal error happened while SMON was doing active transaction recovery.
Mon May 3 18:58:40 2010
Errors in file <DIR>/name_smon_375.trc:
ORA-00600: internal error code, arguments: [15789], [3], [], [], [], [], [], []
SMON: terminating instance due to error 474
Mon May 3 18:58:40 2010
Errors in file <DIR>/name_dbw3_291.trc:
ORA-00474: SMON process terminated with error
Mon May 3 18:58:40 2010
Errors in file <DIR>/name_dbwg_342.trc:
ORA-00474: SMON process terminated with error
Mon May 3 18:58:40 2010
Errors in file <DIR>/name_lmon_35.trc:
ORA-00474: SMON process terminated with error

Changes

 

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.