In this Document
Symptoms |
Cause |
Solution |
References |
APPLIES TO:
Oracle Database - Enterprise Edition - Version 10.2.0.3 to 10.2.0.4 [Release 10.2]Information in this document applies to any platform.
***Checked for relevance on 29-Jun-2013***
SYMPTOMS
While inserting into a table, the following errors are raised:
ORA-07445: exception encountered: core dump [kksumc()+248] [SIGSEGV] [Address not mapped to
object] [0x00000007F] [] []
ORA-00600: internal error code, arguments: [17087], [0x476186E50], [], [], [], [], [], []
object] [0x00000007F] [] []
ORA-00600: internal error code, arguments: [17087], [0x476186E50], [], [], [], [], [], []
Stack from the trace will be similar to the following:
ksedmp <- ssexhd <- sigacthandler <- kksumc <- opiodr <- ttcpip <- opitsk <- opiino <- opiodr <- opidrv <- sou2o <- opimai_real <- main <- start
- OR -
ksedmp <- kgeriv <- kgeasi <- kglivr <- kksfbc <- kkspsc0 <- kksParseCursor <- opiosq0 <- kpooprx <- kpoal8 <- opiodr <- ttcpip <- opitsk <- opiino <- opiodr <- opidrv <- sou2o <- opimai_real <- main <- start
CAUSE
The behavior and stack trace point to Bug 7706062.
This problem is caused by internal latching issues which will raise these errors.
SOLUTION
- Apply any of next patch set / patch bundle where the bug is fixed:
o 10.2.0.5 (Server Patch Set)
o 10.2.0.4 Patch 28 on Windows Platforms
- OR -
- Apply interim Patch 7706062 if available for your platform and Oracle version
- OR -
- As a possible workaround that has worked for some customers, check for invalid objects in the database and validate them.
Please refer to:
Note 158185.1 - How to Resolve Invalid Objects in a Database