As you know if db has lots of redo switch from other days, your archivelog disk can be full. In that point you have 3 options

• Increase disk or change archivelog destination
• Run archivelog backup (In our case we do not follow this method)
• Delete archivelogs by using rman utulity command or rm command.

Always exercise caution when deleting archive logs, especially in a production environment, and ensure you have a proper backup strategy in place. Do not forget Deleting archive logs is irreversible, and it affects your ability to recover the database to a point in time before the logs were deleted. Ensure that you have adequate backups and that deleting these logs won’t impact your recovery requirements.

So first Identify Archive Logs to Delete: Determine which archive logs you want to delete. You can specify a range of logs to delete based on various criteria like sequence numbers, timestamps, etc.

connect rman utulity

DELETE ARCHIVELOG ALL BACKED UP BEFORE ‘SYSDATE – x’;
Replace with the number of days before which you want to keep archive logs.

For example, ‘SYSDATE – 7’ would delete all archive logs backed up more than 7 days ago.

or

You can delete specific archive logs by specifying their sequence numbers:
DELETE ARCHIVELOG ALL COMPLETED BEFORE ”;

or

delete noprompt archivelog until time “sysdate-1/2” backed up 1 times to device type disk << if you are taking backup to disk

Do not forget to run crosscheck archivelog all; command after delete process.