How To Efficiently Drop (or Truncate) A Table With Many Extents
(Doc ID 68836.1)
Last updated on SEPTEMBER 29, 2023
Applies to:Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Information in this document applies to any platform.
This note describes why a user process can consume large amounts of CPU
after dropping a table consisting of many extents, and a potential
workaround to stop the problem occurring. Essentially the CPU is being
used to manipulate the extents i.e. moving used extents (uet$) to free
extents (fet$). In certain circumstances it may be possible to regulate
this CPU activity.
This article is intended to assist DBAs who may need to drop a table consisting of many extents.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!