ORA-600 [1433] Causes Instance Crash (Doc ID 1262865.1)

Last updated on FEBRUARY 07, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.4 to 11.1.0.7 [Release 10.2 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 18-Dec-2013***

Symptoms


=== ODM Issue Clarification ===

Customer receives errors and instance crash during normal operations.

Wed Aug 11 11:59:04 2010
Errors in file /dbs/trace/pcdba/bdump/erebango_lms1_15384.trc:
ORA-00600: internal error code, arguments: [1433], [60], [], [], [], [], [], []
Wed Aug 11 11:59:04 2010
Trace dumping is performing id=[cdmp_20100811115904]
Wed Aug 11 11:59:05 2010
Errors in file /dbs/trace/pcdba/bdump/erebango_diag_15366.trc:
Wed Aug 11 11:59:33 2010
Errors in file /dbs/trace/pcdba/bdump/erebango_lmsc_15433.trc:
ORA-00600: internal error code, arguments: [1433], [60], [], [], [], [], [], []
Wed Aug 11 11:59:35 2010
Errors in file /dbs/trace/pcdba/bdump/erebango_diag_15366.trc:
Wed Aug 11 11:59:38 2010
Errors in file /dbs/trace/pcdba/bdump/erebango_lms1_15384.trc:
ORA-00600: internal error code, arguments: [1433], [60], [], [], [], [], [], []
Wed Aug 11 11:59:38 2010
LMS1: terminating instance due to error 484
Wed Aug 11 11:59:41 2010
Shutting down instance (abort)

The DIAG trace will show a triggered event:

Dump event group for SESSION
10262 trace name CONTEXT level 4000, forever
Dump event group for SYSTEM
10262 trace name CONTEXT level 4000, forever

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms