While managing Oracle databases, encountering the ORA-00257 error can be frustrating, especially during critical operations. This error has to be fixed at earliest as this could lead downtime of the database. This blog post walks you through the steps to resolve this archiver error, explains why it occurs, and shows how to prevent it from recurring.
Table of Contents
Error :
ORA-00257 : archiver error
Cause of ORA-00257 :
1. Archive Destination Got Full :
Issue the below command to check the archive log destination :
show parameter LOG_ARCHIVE_DEST_n
If its in OS file system, check if the filesystem got full :
df -kh
If its in ASM, check the space if any disk space got full :
SELECT name, total_mb, free_mb FROM v$asm_diskgroup;
2.Permissions or file system issues
If any file system is having any issue , then we may face this error. We may need to check with OS Team also if its having permission issue.
3. Due to slow backup/Backup Fail:
If backup is slow or if its failing, then those archivelogs which are not backed up, we may see the backlog and as a result they are not being deleted, and FS got full.
Resolution of ORA-00257 :
Option 1 : Clear archivesogs
Clear the archivelogs which are backed up.
Only do this after verifying backups!
-- In RMAN RMAN> DELETE ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE-1';
Option 2 : Change Archive Dest
Immediately change the location of the archive dest temporarility or move some archives to another location
alter system set log_archive_dest_2='/oradaredo02/tmp/arc';
or,
mv *.arc /oraredo02/tmp/arc
Apart from that, you can check if FRA got full. You can follow the doc for troubleshooting FRA : how to resolve if FRA got full.
Also, you can get more information regarding ORA-00257 from the Oracle Official Doc as well.