Hi John, you can think about deferred log destinations in Data Guard environments. Oracle introduced a hidden parameter (with version 11.2.0.x) called "_deferred_log_dest_is_valid" to control this behavior. More details can be found in MOS ID #1380368.1. Best Regards Stefan Koehler Oracle performance consultant and researcher Homepage: http://www.soocs.de Twitter: @OracleSK > John Hallas <John.Hallas@xxxxxxxxxxxxxxxxxx> hat am 4. Dezember 2014 um 14:51 > geschrieben: > > * Archived redo logs are not eligible for deletion until all the > consumers of the logs have satisfied their requirements. > > I am interested in what consumers of the log files might be in point 4. > Situations I can think of is if GoldenGate has a long-running transaction > which it think might still need an old log file (the system where the > situation occurred does have GG extracting and forwarding on transactions but > we have bnot integrated it with RMAN) or if a LogMiner session is running. I > am not sure I can think of any other situations. Obviously the RMAN > retention policy manages when files become obsolete but they will not show -- //www.freelists.org/webpage/oracle-l