Database Instance Crashes with ORA-600[1433],[60] Errors and MSG59 seen in tracefiles.

(Doc ID 555395.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Server - Enterprise Edition - Version: to
This problem can occur on any platform.


This article is written specifically for 600[1433][60] when seen in conjunction with the following
symptoms :-

a) ORA-00600: internal error code, arguments: [1433], [60]

The above error will be seen in the alert log

b) Current SQL statement for this session will be similar to :-

No specific SQL structure is considered linked to this error/bug when related to this article

c) PLSQL Call Stack wil be similar to :-

As above

d) Stack will be similar to :-

Function List (to Full stack) (to Summary stack)
ksedst <- ksedmp <- ksfdmp <- kgeriv <- kgesiv
<- ksesic1 <- ksaamb <- ksasnd <- ksbasend_internal <- ksbasend
<- kcrfrsn <- kcllwr <- kclpto <- kjmsm <- ksbrdp
<- opirip <- opidrv <- sou2o <- opimai_real <- main <- $START$

KSAAMB must be seen in the stack for this article to be considered fully applicable

e) The ORA-600 trace will report information similar to :-

Dump of message links starting at node c0000002d0a499f0:
Forward Links:
[c0000002cd21ccd0,c0000002d0a499f0]msg 59, length 24
----------> many more of the same here
[c0000002cd1ecaf8,c0000002cd1dfd68]msg 59, length 24
[c0000002cd206fd8,c0000002cd21ccd0]msg 59, length 24
[c0000002cd1dfd68,c0000002cd1dd258]msg 59, length 24
[c0000002cd21ccd0,c0000002d0a499f0]msg 59, length 24
total seen = 3598

The total seen can vary and this article is specific to MSG 59, if a series of any other msg number
is seen the article is unlikely to resolve.


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