Oracle archivelog deletion policy

Here are my posts on the dbi-services blog about archivelog deletion policy.

The deletion policy on a dataguard configuration should be:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;

for the site where you don’t backup. It can be the standby or the primary.

and:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY BACKED UP 1 TIMES TO DISK;

for the site where you do the backups. It can be the primary or the standby.

Some related posts:

Archivelog deletion policy for Standby Database in Oracle Data Guard - Blog dbi services

Drilling down V$RECOVERY_AREA_USAGE - Blog dbi services

Archivelog deletion policy on Data Guard configuration - Blog dbi services

2 ways to move archivelogs - both need RMAN - Blog dbi services

Update 29-SEPT-2019

I’ve updated this post so that the examples mention APPLIED ON STANDBY instead of APPLIED ON ALL STANDBY. The difference is that only the mandatory destinations are considered then. With ON ALL STANDBY the archived logs are kept in recovery area when you disable log shipping for one destination. There no general recommendation: you just need to know what you do. If you disable log shipping for a short period, then you want to keep the archived logs for when you re-enable it. But you will probably not be taking the risk to have the recovery area full and hang the primary for that. Especially in recent versions where you can recover the gap easily.