This script is designed to run against STANDBY databases to deleted applied archives older than specific number of hours defined by the user. It maintains that un-applied archives remain un-touched.
Download the script:
https://www.dropbox.com/s/xx5o6b94rv5ps30/delete_applied_archives_on_standby.sh?dl=0
How to use the script:
e.g. Deleting applied archives older than 24 hours:
LAST_N_HOURS=24
⏩ You can use FORCE option when deleting the archives from RMAN console: [Y|N] [Default is NO]
⏩ You can decide to CROSSCHECK the archivelogs after the archivelogs deletion: [Y|N] [Default is YES]
⏩ Also you can schedule it to run periodically in the Oracle's user crontab as well.
Download the script:
https://www.dropbox.com/s/xx5o6b94rv5ps30/delete_applied_archives_on_standby.sh?dl=0
How to use the script:
⏩ Set MAIL_LIST variable to your E-mail to receive an email alert if archives are not applied.
e.g. MAIL_LIST="john.smith@abc.com"
⏩ Specify the candidate archives for deletion older than N hours by setting LAST_N_HOURS variable to the number of hours.
e.g. MAIL_LIST="john.smith@abc.com"
⏩ Specify the candidate archives for deletion older than N hours by setting LAST_N_HOURS variable to the number of hours.
e.g. Deleting applied archives older than 24 hours:
LAST_N_HOURS=24
⏩ You can EXCLUDE any instance from having the script to run against by passing the INSTANCE_NAME you want to exclude to EXL_DB variable.
e.g. excluding orcl from archive deletion:
EXL_DB="\-MGMTDB|ASM|orcl"
⏩ You can use FORCE option when deleting the archives from RMAN console: [Y|N] [Default is NO]
e.g. FORCE_DELETION=Y
⏩ You can decide to CROSSCHECK the archivelogs after the archivelogs deletion: [Y|N] [Default is YES]
e.g. VALIDATE_ARCHIVES=Y
⏩ Also you can schedule it to run periodically in the Oracle's user crontab as well.
DISCLAIMER: THIS SCRIPT IS DISTRIBUTED IN THE HOPE THAT IT WILL BE USEFUL, BUT WITHOUT ANY WARRANTY. IT IS PROVIDED "AS IS".
although all archivelogs are applied on the standby, the script returns this error:
ReplyDeleteRMAN-08120: warning: archived log not deleted, not yet applied by standby
Even I face the same bug on 12c+ versions, you can simply set the FORCE_DELETION parameter at line 65 to YES, this will forcefully delete the "APPLIED" archives and overcome this bug:
ReplyDeleteFORCE_DELETION=Y