How to work when we get an archive file system alert?

  When we receive an OEM archive file system alert how do we check & resolve.   

   

• If this is STANDALONE database
• Check the Archivelog_log output, look for BACKUP_COUNT =2 & those are the files can be removed safely from DISK using the below RMAN command
1. RMAN> delete archivelog all backed up 2 times to device type 'SBT_TAPE' completed before  'sysdate-7';
2. sysdate –DAY can be modified to 5/6 based on the situation if we are running out of space
• Check the previous day archivelog backup (some DB this is scheduled as a separate script & in some it is part of complete backup) is successful from /nsr/applogs
• If this has not run on the scheduled time or failed call TB networker oncall on +91 7760976961 & ask them to kick off the archivelog backup alone.

• If this is PRIMARY database
• Check the Archivelog_log output, look for BACKUP_COUNT =2 of primary archive file & local remote sequence it should say APPLIED=YES & those are the files can be removed safely from DISK using below RMAN command
1. RMAN> delete archivelog all backed up 2 times to device type 'SBT_TAPE' completed before  'sysdate-7';
2. sysdate –DAY can be modified to 5/6 based on the situation if we are running out of space
• Check the previous day archivelog backup (some DB this is scheduled as a separate script & in some it is part of complete backup) is successful from /nsr/applogs
• If this has not run on the scheduled time or failed call TB networker oncall on +91 7760976961 & ask them to kick off the archivelog backup alone.

• If this is STANDBY database
• Check the Archivelog_log output, look for APPLIED=YES & those are the files can be removed safely from DISK using below RMAN command
1. RMAN> delete archivelog all completed before  'sysdate-7';
2. sysdate –DAY can be modified to 5/6 based on the situation if we are running out of space