Archivelogs Applied to Standby are NOT Deleted from Primary Site After Backup with DELETE INPUT

Symptoms
This is a Data Guard configuration.Logs from primary are shipped to the standby site and there is an apply delay of 24 hours in place.Archivelogs are backed up on the primary site with DELETE INPUT option but occasionally, whenthere is a gap in the log sequence on the standby site (which can be forced by deferring thestandby log destination) rman will stop deleting logs after backup, raising the following warning for every log:WARNING: archive log not deleted, not yet applied by standbyFrom this point onwards, no logs are deleted from the primary site.
The same problem can occur if archiving is interrupted for any reason; once this occurs, no logs from the Primary site can be deleted when 'backup archivelog all delete input' is used.
Cause
Bug 4919478: Some archived logs successfully applied to standby are not removed by RMAN'backup archivelog all delete input' command..
Solution
Do not use 'delete input' option to housekeep archivelogs after backup. Instead:

Change:

RMAN> backup archivelog all delete input;

To something like:

RMAN> backup archivelog all not backed up 2 times;
delete noprompt archivelog until time 'sysdate -2' backed up 2 times to device type sbt;

Change the time spec according to your requirements - this example retains 2 days worth of archivelogs on disk.
This is the recommended method for housekeeping logs in a Data Guard environment - see