ORA-04020: Deadlock Detected While Trying To Lock Object 267 Logging into Database
(Doc ID 2627385.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and laterInformation in this document applies to any platform.
Symptoms
- User not able to login the database due to the error(ORA-04020: deadlock detected while trying to lock object XXX
- Call Stack per hanganalyze report:
'library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock'<='library cache lock' (cycle)
ksedsts <- ksdxfstk <- ksdxcb <- sspuser <- __sighandler
<- thread_wait <- sskgpwwait <- skgpwwait <- ksliwat <- kslwaitctx
<- ksfwaitctx <- kglLockWait <- kgllkal <- kglLock <- kglget
<- kziasfc <- kpolnb <- kpoauth <- opiodr <- ttcpip
<- opitsk <- opiino <- opiodr <- opidrv <- sou2o
<- opimai_real <- ssthrdmain <- main
Changes
Database schema refreshed using EXPDP/IMPDP from another database
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 |