Last updated on MAY 15, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.8 to 12.2.0.1 [Release 9.2 to 12.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - 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.
Symptoms
When we delete the rows from the table using the DELETE command, the extents that are allocated to the table will not be released and the table still holds them, whereas when using TRUNCATE with DROP STORAGE clause (which is default), it will release the space back to tablespace.
See Also
Recover a Dropped Table Using Oracle Flashback DropUsing Flashback Database and Restore PointsTo know which user delete data - Ask TOMFLASHBACK TABLEBut we see cases that event truncating won't release the space back to tablespace.
See Also
Oracle Flashback Best PracticesCause
To view full details, sign in with your My Oracle Support account. | |
Don't have a My Oracle Support account? Click to get started! |
| Symptoms |
| Cause |
| Solution |
