Re: best solution for backup with archivelog mode

I don't think you should be deleting archlogs *before* a backup, whether it's the oldest archlog or not, and whether it's a offline or online backup. Always wait until after the backup completes before you delete anything. Assuming the database shutdown was clean (i.e., a "shutdown immediate" completed without errors) then you can often nuke all archlogs created prior to the backup. The exceptions are when using logminer technologies like Streams and DataGuard, because the capture process tends to start scraping a few SCN before the database's SCN, and that could make Capture go looking in the archlogs. To determine when it's cool to nuke an archlog query DBA_REGISTERED_ARCHIVED_LOG where column PURGEABLE = 'YES'. RMAN and Streams work with this view.

If you are using Flashback Database (as you indicated) then you must be using RMAN already. The only supported way to perform space management of the FRA is with RMAN.

Yes, you can restore a prior backup and roll forward using archlogs. The roll forward will stop when Oracle encounters a missing archlog and you can never get past that point. Having the "last" archlog is not good enough. You must have all archlogs from your last backup until the point you wish to recover. If you last backup was hot then you also need all archlogs generated during the last hot backup. Received on Mon Apr 30 2007 - 13:16:50 CDT