Oracle Delete input with delete all input

Oracle Official Documentation Tips:
If you had specifiedDELETE INPUTRather than DELETE all INPUT, thenRMAN would has only deleted the specific archived redo log files, it backed up. For example, RMAN would delete the logs in/arc_dest1 if these files were used as the source of the backup, but leave the Contents of The/arc_dest2 intact
If delete input is specified, Rman will delete only the archived logs that have been backed up, for example, if there are two archive directories/arc_dest1 and/arc_dest2 if/arc_dest1 is the source of backup, delete input deletes/arc_ Dest1 in the content, retain the archive log in the Dest2, through the experiment can be seen, even if there are two archive location, Rman backup seems to be the log file as the source, the backup log deleted.
------------------------------------------------------------
If you had specifiedDELETE all INPUTRMAN backs up only one copy of each log sequence number in these archiving locations.it deletes all copies of any log that It backed up from the other archiving destinations
If you specify delete all input Rman will only back up the log sequence number in all archive directories, and Rman deletes all archive logs in Dest1 and Dest2.
Conclusion: There is no difference between only one archive catalog delete input and delet all input.

==================
Observe the following two backup statements
1) Backup as compressed backupset filesperset 4 Incremental level=1 cumulative database plus archivelog Delete input;
2) Backup as compressed Backupset filesperset 4 Incremental Level 1 database;
Backup as compressed backupset archivelog all delete all input;
Statement 1 is a cumulative backup, and statement 2 is a differential 1 backup. After the backup is finished, you want to back up the archive log while deleting the archived log that was backed up. The difference is that statement 1 uses delete input, Statement 2 uses the delete all input
A column, such as Weeks 1, 2, and 4, uses statement 2 to make a differential backup. Week 3 Use statement 1 for cumulative backups. This way, 1, 2 will only back up the archive log generated by the day, and Week 3 will only back up the archived logs generated on the same day, and Week 4 will back up the archived logs generated by week 3 and 42 days.
The reason for this is that the archive log itself is multiplexed, that is, the creation of archived logs in the FRA, as well as the creation of archive logs in other paths. Delete Input only deletes the default path, the archive log in the FRA, and the archive logs in the other paths are retained. So when you back up archive logs on Week 4, the archive logs that were kept in the other paths are backed up at the same time as the archived logs that are generated today. This situation causes the archive log to be backed up repeatedly, wasting storage resources.
So when multiplexing is implemented for archived logs, you should use delete all input to clean up the archived logs

Oracle Delete input with delete all input