Ksdxcb Debug Message in The Alert Log File
(Doc ID 1192063.1)
Last updated on AUGUST 10, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 and laterInformation in this document applies to any platform.
Symptoms
Trace file generated with the following info :
*** SESSION ID:(111.6748) 2010-08-04 06:43:40.808
ksdxcb(): unknown reason = 0x0
(debug info) pso: 5cd00c620 state: DONE
num_executed: 0 rsn: REASON_INVALID
debugger waiting?: NO pid: Unix process pid: 0, image:command:
*** 2010-08-04 06:43:40.811
ksedmp: internal or fatal error
And with the "Call Stack Trace" :
ksedmp <- ksdxcb <- sspuser <- sighndlr <- call_user_handler<- sigacthandler <- syscall6 <-sskgpwwait <- ksliwat
<- kslwaitns_timed<- kskthbwt <- kslwait <- kkjsexe <- kkjrdp <- opirip<- opidrv <- sou2o <- opimai_real <- 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 |