My Oracle Support Banner

ORA-600 [510] [] [KCL gc element parent latch] Causing Instance Crash (Doc ID 1378992.1)

Last updated on MARCH 09, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.5 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Database crashes due to ORA-600: [510], [0x35AC3E358], [KCL gc element parent latch].

The following was reported in the alert log:

Sat Aug 06 17:41:00 PDT 2011
Errors in file <oracle_base>/admin/<instname>/bdump/<instname>_dbw0_18538.trc:
ORA-00600: internal error code, arguments: [510], [0x35AC3E358], [KCL gc element parent latch], [], [], [], [], []
Sat Aug 06 17:41:01 PDT 2011
Errors in file <oracle_base>/admin/<instname>/bdump/<instname>_dbw0_18538.trc:
ORA-00600: internal error code, arguments: [510], [0x35AC3E358], [KCL gc element parent latch], [], [], [], [], []
Sat Aug 06 17:41:01 PDT 2011
DBW0: terminating instance due to error 471


Trace file shows a call stack similar to the following during the time of the error:

kslfre <- kclfwrite1 <- kcbbwrdone <- kcbbic1 <- kcbbiop <- kcbbdrv <- ksbabs <- ksbrdp <- opirip <- opidrv <- sou2o <- opimai_real <- main <- libc_start_main <- start


The function kclfwrite1 calling kslfre is typical for this problem.

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.