Delayed Block Cleanout is Not Working as Expected
(Doc ID 1925688.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 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
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 21-Jul-2017***
Delayed Block Cleanout isn't working as expected. Select right after a delete would clean out the left off transactional information, this should happen once and subsequent selects should not have to clean up the information.
But it has been observed that, sometimes (both in 11g and 12c) , on every select after a DML operation, cleanout happens. Also it appears that no cleanup is happening at the commit.
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