Subscribe to Posts by Email

Subscriber Count

    701

Disclaimer

All information is offered in good faith and in the hope that it may be of use for educational purpose and for Database community purpose, but is not guaranteed to be correct, up to date or suitable for any particular purpose. db.geeksinsight.com accepts no liability in respect of this information or its use. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content and if notify any such I am happy to remove. Product and company names mentioned in this website may be the trademarks of their respective owners and published here for informational purpose only. This is my personal blog. The views expressed on these pages are mine and learnt from other blogs and bloggers and to enhance and support the DBA community and this web blog does not represent the thoughts, intentions, plans or strategies of my current employer nor the Oracle and its affiliates or any other companies. And this website does not offer or take profit for providing these content and this is purely non-profit and for educational purpose only. If you see any issues with Content and copy write issues, I am happy to remove if you notify me. Contact Geek DBA Team, via geeksinsights@gmail.com

Pages

Dataguard or RMAN: Archivelog deletions when you have standby databases

Normally, archived redo log files in a flash recovery area that were backed up to a tertiary device or made obsolete (as defined by the RMAN retention policy) are eligible for deletion.

The archived redo log files that are backed up or obsolete can eventually be deleted automatically to make space if the disk space in the flash recovery area becomes full.

However, you can change this default deletion policy using the following

RMAN command:CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];

This will be especially useful when you have bunch of archivelogs and you are unable to deterime which archives applied or not, Further, there will be cases when you have manually recovered the archive logs using recover standby rather managed recovery and the v$archived_log applied column will be marked as "NO"

APPLIED ON STANDBY:-

CLEAR Clause

Use the CLEAR clause to disable the deletion policy that was previously set up with the RMAN CONFIGURE ARCHIVELOG DELETION POLICY command. The Oracle database will resume the default deletion policy behavior, which is to delete archived redo log files that are backed up or obsolete to make space if disk space in the flash recovery area becomes full.

Using the NONE Clause

Use the NONE clause so that archived redo logs in flash recovery area that were backed up or obsolete as per the RMAN retention policy are eligible for deletion. This is the default configuration. Archived redo log files that are backed up or obsolete are deleted to make space if the disk space in the flash recovery area becomes full.

Examples of the CONFIGURE ARCHIVELOG DELETION POLICY Command

When backups of archived redo log files are taken on the standby database:

  1. Issue the following command on the primary database:

    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    
  2. Issue the following command on the standby database:

    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    

When backups of archived redo log files are taken on the primary database:

  1. Issue the following command on the standby database:

    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    
  2. Issue the following command on the primary database:

    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    
Regards
Geek DBA

2 comments to Dataguard or RMAN: Archivelog deletions when you have standby databases