.
\nThe deletion policy on a dataguard configuration should be:
\nCONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;\nfor the site where you don’t backup. It can be the standby or the primary.
\nand:
\n\nCONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY BACKED UP 1 TIMES TO DISK;\nfor the site where you do the backups. It can be the primary or the standby.
\nI’ve always configured it in this way, but I recently discovered that the order of the subclause matters. Do not CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK APPLIED ON ALL STANDBY; because no archivelogs will be reclaimable, and your recovery area will be full. This is probably a bug. I’ll update this post when I have more information about this.
\n\nI’m on the standby database where I do the backups:
\n\n \nRecovery Manager: Release 12.2.0.1.0 - Production on Sun Oct 22 17:37:18 2017\n \nCopyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved.\n \nRMAN-06568: connected to target database: CDB2 (DBID=693620717, not open)\n \nRMAN> \nRMAN-03029: echo set on\n \nI start with all default configuration:
\n\nRMAN> show all;\nRMAN-06607: RMAN configuration parameters for database with db_unique_name CDB2B are:\nRMAN-01005: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default\nRMAN-01005: CONFIGURE BACKUP OPTIMIZATION OFF; # default\nRMAN-01005: CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default\nRMAN-01005: CONFIGURE CONTROLFILE AUTOBACKUP ON; # default\nRMAN-01005: CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default\nRMAN-01005: CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default\nRMAN-01005: CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\nRMAN-01005: CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default\nRMAN-01005: CONFIGURE MAXSETSIZE TO UNLIMITED; # default\nRMAN-01005: CONFIGURE ENCRYPTION FOR DATABASE OFF; # default\nRMAN-01005: CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default\nRMAN-01005: CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default\nRMAN-01005: CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default\nRMAN-01005: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default\nRMAN-01005: CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/12.2.0/dbhome_1/dbs/snapcf_CDB2B.f'; # default\nI have one full backup and then some archivelog backups:
\n\nRMAN> list backup summary;\nRMAN-06345: List of Backups\nRMAN-06346: ===============\nRMAN-06347: Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag\nRMAN-06348: ------- -- -- - ----------- --------------- ------- ------- ---------- ---\nRMAN-06349: 9 B F A DISK 22-OCT 17:05:16 1 1 NO TAG20171022T170250\nRMAN-06349: 10 B F A DISK 22-OCT 17:06:23 1 1 NO TAG20171022T170250\nRMAN-06349: 11 B F A DISK 22-OCT 17:07:18 1 1 NO TAG20171022T170250\nRMAN-06349: 12 B F A DISK 22-OCT 17:07:35 1 1 NO TAG20171022T170732\nRMAN-06349: 13 B A A DISK 22-OCT 17:15:09 1 1 NO TAG20171022T171502\nRMAN-06349: 14 B F A DISK 22-OCT 17:15:19 1 1 NO TAG20171022T171518\nRMAN-06349: 15 B A A DISK 22-OCT 17:27:28 1 1 NO TAG20171022T172721\nRMAN-06349: 16 B F A DISK 22-OCT 17:27:39 1 1 NO TAG20171022T172737\nI have no obsolete backups:
\n\nRMAN> report obsolete;\nRMAN-06524: RMAN retention policy will be applied to the command\nRMAN-06511: RMAN retention policy is set to redundancy 1\nRMAN-06147: no obsolete backups found\nI have 1.8% of the recovery area that has been applied:
\n\nRMAN> configure archivelog deletion policy to applied on all standby;\nRMAN-06601: new RMAN configuration parameters:\nRMAN-01005: CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;\nRMAN-06604: new RMAN configuration parameters are successfully stored\n \n \nRMAN> select percent_space_used,percent_space_reclaimable,number_of_files from v$recovery_area_usage where file_type='ARCHIVED LOG';\nRMAN-01005: PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES\nRMAN-01005: ------------------ ------------------------- ---------------\nRMAN-01005: 1.3 1.08 3\nI have 1.3% of the recovery area that has been backed up:
\n\nRMAN> configure archivelog deletion policy to backed up 1 times to disk;\nRMAN-06600: old RMAN configuration parameters:\nRMAN-01005: CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;\nRMAN-06601: new RMAN configuration parameters:\nRMAN-01005: CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK;\nRMAN-06604: new RMAN configuration parameters are successfully stored\n \n \nRMAN> select percent_space_used,percent_space_reclaimable,number_of_files from v$recovery_area_usage where file_type='ARCHIVED LOG';\nRMAN-01005: PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES\nRMAN-01005: ------------------ ------------------------- ---------------\nRMAN-01005: 1.3 1.3 3\nThis looks good. I have some archived logs that have been applied but not backed up yet.
\nBut now I want to combine both:
\n\nRMAN> configure archivelog deletion policy to backed up 1 times to disk applied on all standby;\nRMAN-06600: old RMAN configuration parameters:\nRMAN-01005: CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK;\nRMAN-06601: new RMAN configuration parameters:\nRMAN-01005: CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK APPLIED ON ALL STANDBY;\nRMAN-06604: new RMAN configuration parameters are successfully stored\n \n \nRMAN> select percent_space_used,percent_space_reclaimable,number_of_files from v$recovery_area_usage where file_type='ARCHIVED LOG';\nRMAN-01005: PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES\nRMAN-01005: ------------------ ------------------------- ---------------\nRMAN-01005: 1.3 0 3\nNothing is recoverable here, wich is in my opinion a bug.
\nTrying the same but with different order:
\n\nRMAN> configure archivelog deletion policy to applied on all standby backed up 1 times to disk;\nRMAN-06600: old RMAN configuration parameters:\nRMAN-01005: CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK APPLIED ON ALL STANDBY;\nRMAN-06601: new RMAN configuration parameters:\nRMAN-01005: CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY BACKED UP 1 TIMES TO DISK;\nRMAN-06604: new RMAN configuration parameters are successfully stored\n \n \nRMAN> select percent_space_used,percent_space_reclaimable,number_of_files from v$recovery_area_usage where file_type='ARCHIVED LOG';\nRMAN-01005: PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES\nRMAN-01005: ------------------ ------------------------- ---------------\nRMAN-01005: 1.3 1.08 3\nThis look good. 1.08% have been applied and backed up.
\nI’ve verified the same behavior when backups are done on primary, or on standby, and same in 11.2.0.4, 12.1 and 12.2 with latest RU.
\nWhen the deletion policy is starting with the backup clause before the standby clause, the files are not marked as reclaimable. However, they are deleted with a ‘delete archivelog’ statement without the ‘force’ option.
\nThe behavior is the same with ‘shipped to’ instead of ‘applied on’.
Be careful with the syntax: the ‘applied’ or ‘shipped’ clause must be written before the ‘backup’ one.
\nCheck that archived logs are reclaimable. The query I use for that is in: https://www.dbi-services.com/blog/archivelog-deletion-policy-for-standby-database-in-oracle-data-guard/. When more archived log detail is required, I’ve also this query: https://www.dbi-services.com/blog/drilling-down-vrecoveryareausage/
\nAlways have a look at the recovery area usage after you change the deletion policy, the site where you backup, or after a switchover.