ORA-00600[Kksfbc-Reparse-Infinite-Loop] WHEN RUNNING BATCH JOB (Doc ID 566838.1)

Last updated on NOVEMBER 28, 2016

Applies to:

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

Symptoms

The following symptoms will be seen :-

a) SQL or some batchcode consistently fails with ORA-00600 reported in alert similar to :-

ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [0x2A97676CF8], []

b) Stack trace will be similiar to the following :-

Function List (to Full stack) (to Summary stack)
ksedst <- ksedmp <- ksfdmp <- kgerinv <- kgeasnmierr
<- kksfbc <- opiexe <- opipls <- opiodr <- rpidrus
<- skgmstack <- rpidru <- rpiswu2 <- rpidrv <- psddr0
<- psdnal <- pevm_EXECC <- pfrinstr_EXECC <- pfrrun_no_tool <- pfrrun
<- plsql_run <- peicnt <- kkxexe <- opiexe <- Cannot
<- Cannot <- Cannot <- kpoal8 <- opiodr <- ttcpip
<- opitsk <- opiino <- opiodr <- opidrv <- sou2o
<- opimai_real <- main

The stack itself for this ORA-00600 is quite generic and does not easily narrow the bug
search, on this basis the next symptom is very important for this article to be considered appropriate.

c) The ORA600 trace will show a 'state object' containing NORFINV eg :-

SO: 0x1c4406d60, type: 53, owner: 0x1dfef9708, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=1c4406d60 handle=1cb1f64c0 mode=N
call pin=(nil) session pin=(nil) hpc=0000 hlc=0000
htl=0x1c4406de0[0x1ced30c88,0x1ced30c88] htb=0x1ced30c88 ssga=0x1ced30830
user=1dfef9708 session=1dfef9708 count=0 flags=LRU/[4000] savepoint=0x13ad
LIBRARY OBJECT HANDLE: handle=1cb1f64c0 mtx=0x1cb1f65f0(0) cdp=0
name=<SCHEMA>.<TABLE_NAME>  --------------------------------------------> {*}
hash=6d9d67d457022d28dbc65f7fb8f7fa34 timestamp=05-01-2008 19:56:43
namespace=TABL flags=KGHP/TIM/XLR/NORFINV/[00000028]

{*} : The table itself is a partitioned table, if not and NORFINV is still seen with the other symptoms
the article can still be considered but is not guaranteed to solve.

d) Problem is resolved and flush of shared pool or a bounce of the database but then can come back again and no obvious manner of what operations lead up to getting the database into an internal state
where the ORA-00600 can be raised.

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