My Oracle Support Banner

ORA-07445: exception encountered: core dump [expepr()+00f4] (Doc ID 986731.1)

Last updated on JULY 03, 2023

Applies to:

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

Symptoms

 

Encountered the following error in the alert.log

ORA-07445: exception encountered: core dump [expepr()+00f4] [SIGSEGV] [ADDR:0x1F0000000A] [PC:0x1038E9394] [Address not mapped to object] []

Call stack in trace file shows:

----- Call Stack Trace -----
 skdstdst <- ksedst1 <- ksedst <- dbkedDefDump <- ksedmp
       <- ssexhd <- 44c0 <- evacssr <- set_start_position <- qerwnFetch
        <- qervwFetch <- qerwnFetch <- qervwFetch <- rwsfcd <- qerltcFetch
         <- insexe <- 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 <- start


Note: A CASE statement is associated with the query in the trace associated with the error.  In this case, there was PL/SQL code associated with the execution of the SQL statement in the trace file.  The PL/SQL code contained the CASE statement but this could not be seen in the trace.



The issue can also manifest itself with this call stack:

skdstdst <- ksedst1 <- ksedst <- dbkedDefDump <- ksedmp       <- ssexhd <- 53552D49 <- evacssr <- BFFEE934 <- qmsqx_evaopn    <- qmsqxStreamEvalXMLO <- qmsqxEvalXMLOp <- evaopn2 <- evadcd <- qesaAggNonDistSS <- PGOSF590_qerjoRow <- Procedure <- GOSF574_qervwRow <- Procedure <- qertbFetchByRowID  <- qerjotFetch <- qervwFetch <- qerjoFetch <- qergsFetch <- opifch2 <- opifch <- opipls <- opiodr <- PGOSF137_rpidrus <- skgmstack<- rpidru <- rpiswu2 <- rpidrv <- psddr0 <- psdnal <- pevm_BFTCHC <- pfrinstr_FTCHC <- pfrrun_no_tool <- pfrrun <- plsql_run  <- peidxr_run <- peidxexe <- kkxdexe <- kkxmpexe <- kgmexwi <- kgmexec .....

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
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.