ORA-00257: archiver error. Connect AS SYSDBA only, until resolved.
Index
Cause:
The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is the destination device is out of space to store the redo log file.
Remediation :
There are two options to resolve the issue.
First Option :
To show database archive mode –
SQL> archive log list;
Now, you can find archive destinations by USE_DB_RECOVERY_FILE_DEST :
SQL> show parameter db_recovery_file_dest;
The next step in resolving ORA-00257 is to find out what value is being used fordb_recovery_file_dest_size, use:
SQL> SELECT * FROM V$RECOVERY_FILE_DEST;
You may find that the SPACE_USED is the same as SPACE_LIMIT, if this is the case, to resolve ORA-00257 should be remedied by moving the archive logs to some other destination or by taking the RMAN backup and delete the same.
You next need to archive the log files by,
SQL> alter system archive log all;
It is important to note that within step five of the ORA-00257 resolution, you may also encounter ORA-16020 in theLOG_ARCHIVE_MIN_SUCCEED_DEST, and you should use the proper archivelog path and use (keeping in mind that you may need to take extra measures if you are using Flash Recovery Area as you will receive more errors if you attempt to use LOG_ARCHIVE_DEST):
SQL>alter system set LOG_ARCHIVE_DEST_.. = ‘location=/archivelogpath reopen’;
The last step in resolving ORA-00257:Archiver Error is to change the logs for verification using:
SQL> alter system switch logfile;
Second Option :
If you have space in the file system you can try this options also.
ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=<NUMERIC VALUE>G;
This numeric value should be greater than the value already specified for the said parameter.