Getting An Enromous Amount Of Trace Files Generated Showing A SQL Being Run And A Call Stack Trace. (Doc ID 1199014.1)

Last updated on DECEMBER 02, 2019

Applies to:

Symptoms

You could be getting a lot of traces generated, filling up the alert log as below:

Fri Sep 3 05:05:48 2010
Errors in file /u01/app/oracle/product/db10g/admin/<sid>/udump/orcl_ora_15618.trc:
Fri Sep 3 05:05:52 2010
Errors in file /u01/app/oracle/product/db10g/admin/<sid>/udump/orcl_ora_15618.trc:
Fri Sep 3 05:05:54 2010
Errors in file /u01/app/oracle/product/db10g/admin/<sid>/udump/orcl_ora_15618.trc:
Fri Sep 3 05:05:55 2010
Errors in file /u01/app/oracle/product/db10g/admin/<sid>/udump/orcl_ora_15653.trc:

And the trace itself has the following call stack trace:

ksedst <- ksedmp <- kdiknf <- kdimod0 <- kauupd <- updrow <- qerupRow <- Procedure <- qerupFetch <- updaul <- updThreePhaseExe <- 277 <- updexe <- opiexe <- opipls <- opiodr <- rpidrus <- skgmstack <- rpidru <- rpiswu2 <- rpidrv <- psddr0 <- psdnal <- pevm_EXECC <- pfrinstr_
<- EXECC <- pfrrun_no_tool <- pfrrun <- plsql_run <- peicnt <- kkxexe <- opiexe <- kpoal8 <- opiodr <- ttcpip <- opitsk <- opiino <- opiodr <- opidrv <- sou2o <- opimai_real <- main <- libc_start_main

The trace file will also show a part like the below:

*** SESSION ID:(113.1417) 2010-09-06 11:34:27.434
oer 8102.2 - obj# 60445, rdba: 0x01405e5e(afn 5, blk# 24158)
kdk key 8102.2:
ncol: 4, len: 22
key: (22):

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.