Last updated on NOVEMBER 28, 2016
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.3 and later
Information in this document applies to any platform.
***Checked for relevance on 19-Dec-2013***
The following symptoms have been attributed to this issue:
a) Running on a Windows based platform. The bug covered in this article is Windows port specific.
b) Alert log may report an ORA-60 error:
But if no ORA-60 is seen in the alert the article can still be considered applicable provided all other symptoms are met.
c) Alert log will report ORA-07445 error:
[PC:0x9CAE45] [ADDR:0x1C] [UNABLE_TO_READ] 
The ORA-7445 may be reported in different ways depending on platform, typically 'kxsdcbc' will be reported but if not, the trace file should be looked at in more detail.
d) ORA-07445 tracefile will report a 'deadlock' graph/message:
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
e) The call stack trace will be similar to:
<- ktagetg0 <- ktagetp <- ktagetg <- ktagdw <- ktaadm <- kksfbc <- opiexe <- opipls <- opiodr <- rpidrus
<- rpidru <- rpiswu2 <- rpidrv <- psddr0 <- psdnal <- pevm_EXECC <- pfrinstr_EXECC <- pfrrun_no_tool <- pfrrun <- plsql_run
<- peicnt <- kkxexe <- opiexe <- kpoal8 <- opiodr <- ttcpip <- opitsk <- opiino <- opiodr <- opirip
<- opidrv <- sou2o <- opimai_real <- opimai <- BackgroundThreadStart
The key function for this article to be considered is 'kxsdcbc', if this is not seen in the stack the note is unlikely to provide a resolution.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms