ORA-600[1100] Followed By Instance Termination By PMON
(Doc ID 457558.1)
Last updated on MARCH 21, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.3 [Release 10.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
***Checked for relevance on 24-Dec-2013***
Symptoms
A one time error terminated the instance. The alert log shows:
ORA-00600: internal error code, arguments: [1100], [0x52EB9474], [0x57BE84E0], [], [], [], [], []
PMON: terminating instance due to error 472
ORA-00472: PMON process terminated with error
Instance terminated by PMON, pid = 31489
PMON: terminating instance due to error 472
ORA-00472: PMON process terminated with error
Instance terminated by PMON, pid = 31489
The trace file shows an UPDATE was the failing statement.
Trace file gives this message:
Badly formed linked list (header=52eb9474, link=57bd5098):
The function stack also indicates a problem with a link list.
ksedst <- ksedmp <- ksfdmp <- kgeriv <- kgesiv <- kgesic2 <- kggchk <- kcbso1 <- kcbpsod <- kcbget <- ktbxchg <- kdifind <- kdiins0 <- kdiins <- kauupd <- updrow <- PGOSF357_qerupRow <- Procedure <- qerupFetch <- qerstFetch . . . .
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 |