Standby Database Throws ORA-00600 [504], [0x060018F10], [256], [7], [file number translation table], [0], [0], [0x000000000], [], [], [], [] And Redo Apply Stops (Doc ID 1531569.1)

Last updated on FEBRUARY 07, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2 and later
Information in this document applies to any platform.

Symptoms

After adding some tempfiles to your Standby database, the Standby alertlog starts reporting errors:

 

ORA-00600: internal error code, arguments: [504], [0x060018F10], [256], [7], [file number translation table], [0], [0], [0x000000000], [], [], [], []

 

The trace file will show the following:

 

----- Beginning of Customized Incident Dump(s) -----
*** LATCH HIERARCHY ERROR ***
An attempt to get the 'file number translation table' latch at level 7 (address = 0x60018f10)
from location 'krt.h LINE:1266 ID:krta2rl' (also see call stack below)
conflicts with the following held latch(es):
Level 8: 'lock DBA buffer during media recovery' (child #12) (address = 0x9eec10f0)
 gotten from location 'krc2.h LINE:802 ID:lock DBA buffer for write'

 

And the stack trace will show:

skdstdst <- ksedst1 <- ksedst <- dbkedDefDump <- ksedmp <- ksfdmp <- dbgexPhaseII <- dbgexExplicitEndInc <- dbgeEndDDEInvocatio <- nImpl <- dbgeEndDDEInvocatio <- ksl_level_check <- kslgetl <- krta2rl <- krta2r <- krta2rfn <- krcput <- krcput_stby <- kcbr_media_apply <- krp_slave_apply <- krp_slave_main <- ksvrdp <- opirip <- opidrv <- sou2o <- opimai_real <- ssthrdmain <- main <- libc_start_main <- start

 



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