Large Waits on "Enq: TX - Index Contention" While a Massive Delete Takes Place or is Uncomitted
(Doc ID 2281781.1)
Last updated on DECEMBER 11, 2020
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database 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
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
- Index block splits take a large amount of time after a massive delete operation or with a highly fragmented index
- The high amount of time appears because large index block reject count before the segment is extended or a block split occurs
- This issue can cause enq :TX index contention waits in environment where large deletes or index fragmentation occur without the possibility to rebuild/coalesce indexes after it
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