How to Identify the Object Associated with an ORA-600[kqllod:no stub for dependency parent] Error?
(Doc ID 2489137.1)
Last updated on FEBRUARY 15, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterInformation in this document applies to any platform.
Goal
Running utlrp.sql failed with the following error in the alert log:
ORA-00600: internal error code, arguments: [kqllod:no stub for dependency parent], [], [], [], [], [], [], [], [], [], [], []
The associated incident trace file shows the following Current SQL Statement:
begin dbms_utility.validate(:1,:2,:3,:4); end;
as well as the following PL/SQL Call Stack:
----- PL/SQL Call Stack -----
object line object
handle number name
70001049e859bb8 1294 package body SYS.DBMS_UTILITY
7000104387b8658 1 anonymous block
700010449f73300 413 package body SYS.UTL_RECOMP
700010449f73300 559 package body SYS.UTL_RECOMP
700010449f73300 807 package body SYS.UTL_RECOMP
70001043506cf78 1 anonymous block
7000104838ae3f8 857 package body APPS.AD_ZD
700010445494be0 2 anonymous block
object line object
handle number name
70001049e859bb8 1294 package body SYS.DBMS_UTILITY
7000104387b8658 1 anonymous block
700010449f73300 413 package body SYS.UTL_RECOMP
700010449f73300 559 package body SYS.UTL_RECOMP
700010449f73300 807 package body SYS.UTL_RECOMP
70001043506cf78 1 anonymous block
7000104838ae3f8 857 package body APPS.AD_ZD
700010445494be0 2 anonymous block
and the following Call Stack Trace:
skdstdst <- ksedst1 <- ksedst <- dbkedDefDump <- ksedmp
<- ksfdmp <- dbgexPhaseII <- dbgexProcessError <- dbgeExecuteForError <- dbgePostErrorKGE
<- 1244 <- dbkePostKGE_kgsf <- kgeadse <- kgerinv_internal <- kgerinv
<- kgeasnmierr <- kqlLoadDependencies <- kqllod_new <- kqlCallback <- kqllod
<- kglobld <- kglobpn <- kglpim <- IPRA <- kglgob
<- psd_validate <- pevm_icd_call_commo <- pfrinstr_ICAL <- pfrrun_no_tool <- pfrrun
<- plsql_run <- peicnt <- kkxexe <- opiexe <- opipls
<- opiodr <- rpidrus <- skgmstack <- rpidru <- rpiswu2
<- rpidrv <- psddr0 <- psdnal <- pevm_EXIM <- pfrinstr_EXIM
<- pfrrun_no_tool <- pfrrun <- plsql_run <- peicnt <- kkxexe
<- opiexe <- opipls <- opiodr <- rpidrus <- skgmstack
<- rpidru <- rpiswu2 <- rpidrv <- psddr0 <- psdnal
<- pevm_EXIM <- pfrinstr_EXIM <- pfrrun_no_tool <- pfrrun <- plsql_run
<- peicnt <- kkxexe <- opiexe <- kpoal8 <- opiodr
<- ttcpip <- opitsk <- opiino <- opiodr <- opidrv
<- sou2o <- opimai_real <- ssthrdmain <- main <- start
<- ksfdmp <- dbgexPhaseII <- dbgexProcessError <- dbgeExecuteForError <- dbgePostErrorKGE
<- 1244 <- dbkePostKGE_kgsf <- kgeadse <- kgerinv_internal <- kgerinv
<- kgeasnmierr <- kqlLoadDependencies <- kqllod_new <- kqlCallback <- kqllod
<- kglobld <- kglobpn <- kglpim <- IPRA <- kglgob
<- psd_validate <- pevm_icd_call_commo <- pfrinstr_ICAL <- pfrrun_no_tool <- pfrrun
<- plsql_run <- peicnt <- kkxexe <- opiexe <- opipls
<- opiodr <- rpidrus <- skgmstack <- rpidru <- rpiswu2
<- rpidrv <- psddr0 <- psdnal <- pevm_EXIM <- pfrinstr_EXIM
<- pfrrun_no_tool <- pfrrun <- plsql_run <- peicnt <- kkxexe
<- opiexe <- opipls <- opiodr <- rpidrus <- skgmstack
<- rpidru <- rpiswu2 <- rpidrv <- psddr0 <- psdnal
<- pevm_EXIM <- pfrinstr_EXIM <- pfrrun_no_tool <- pfrrun <- plsql_run
<- peicnt <- kkxexe <- opiexe <- kpoal8 <- opiodr
<- ttcpip <- opitsk <- opiino <- opiodr <- opidrv
<- sou2o <- opimai_real <- ssthrdmain <- main <- start
How can the bad object causing this problem be identified?
Solution
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
| Goal |
| Solution |
| References |