Performance Impact of Detecting a Deadlock
(Doc ID 285270.1)
Last updated on FEBRUARY 12, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 8.0.3 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
To increase awareness of the performance impact that deadlock detection can have on an instance.
This article does not cover any material about how to solve deadlocks, just how Oracle detects them and how this detection impacts the overall performance. It is intended for Application Developers, DBA's, Consultants and Support Engineers.
Checked for relevance 20th June 2012
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!