Query Errors with ORA-07445 [kkoosoel()+62]
(Doc ID 2468342.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterInformation in this document applies to any platform.
Symptoms
- Query errors with ORA-7445[kkoosoel()+62] on 12.2.0.1
- If the or condition is commneted out in the SQL statement, the issue disappeared:
SQL> ho diff test.sql t00.sql13c13
< OR TableXX.xxx< '20180123')
---
> )-- OR TableXX.xxx< '20180123')
- Tracefile shows following functions:
ORA-07445: exception encountered: core dump [kkoosoel()+62] [SIGSEGV] [ADDR:0x0] [PC:0x1A15E1E] [Address not mapped to object] []
========= Dump for incident 106465 (ORA 7445 [kkoosoel]) ========
----- Beginning of Customized Incident Dump(s) -----
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst <- dbkedDefDump <- ksedmp <- ssexhd <- sslssSynchHdlr
<- sslsshandler <- sighandler <- kkoosoel <- kkoqbc <- apakkoqb
<- apaqbdDescendents <- apaqbd <- kkqctFullCostTransf <- kkqctdrvORE <- QB
<- kkqoregdtr <- qksqbApplyToQbc <- kkqctdrvTD <- kkqoredrv <- kkqdrv
<- kkqctdrvIT <- apadrv <- opitca <- kksFullTypeCheck <- rpiswu2
<- kksLoadChild <- kxsGetRuntimeLock <- kksfbc <- kkspsc0 <- kksParseCursor
<- opiosq0 <- kpooprx <- kpoal8 <- opiodr <- ttcpip
<- opitsk <- opiino <- opiodr <- opidrv <- sou2o
<- opimai_real <- ssthrdmain <- main <- libc_start_main <- start
Changes
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 |
Changes |
Cause |
Solution |
References |