Flashback Logs Not Deleted when _OMF is disabled.
(Doc ID 2162982.1)
Last updated on JANUARY 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 and laterOracle 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
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the
Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual
environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Directory Name: C:\ORACLEXE\APP\ORACLE\FAST_RECOVERY_AREA and sub-directories.
Database Name: PROD
*************
Sometimes, flashback logs does not get deleted even after dropping the restore points or by Turning off the flashback.
Changes
_omf = disabled
By default _omf is enabled. Due to business requirement or due to some other reason like Oracle database managed by SAP tool, _OMF parameter is disabled explicitly.
https://community.oracle.com/message/10687985#10687985
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |