// Oracle error reference

ORA-00257: archiver error

The archiver can't write archived redo logs, usually because the archive destination or fast recovery area is full. Only SYSDBA can connect until it's resolved.

Error code
ORA-00257
Category
Space, memory and limits
Error message
Archiver error. Connect AS SYSDBA only until resolved.

What it means

In ARCHIVELOG mode, a redo log can't be reused until it has been archived. If archiving stops, redo fills up and the database stops accepting changes. The message is Archiver error. Connect AS SYSDBA only until resolved.

Common causes

  • The fast recovery area or archive destination is full.
  • DB_RECOVERY_FILE_DEST_SIZE is too small for the volume of redo.
  • The archive destination is unavailable, for example an unmounted file system.

How to fix it

  1. Check recovery area usage.

    SELECT space_limit/1024/1024 AS limit_mb, space_used/1024/1024 AS used_mb
    FROM v$recovery_file_dest;
  2. Back up and delete archived logs with RMAN (never delete them by hand with operating-system commands): BACKUP ARCHIVELOG ALL DELETE INPUT;

  3. Or give the recovery area more room.

    ALTER SYSTEM SET db_recovery_file_dest_size = 200G SCOPE = BOTH;

Related errors

More space, memory and limits errors

The code and message text are from the Oracle Database Error Help. Browse the full Oracle error list or search every database error.

// fewer errors, faster fixes

Work on Oracle in SQLly

A native SQL client for macOS, Windows and Linux with schema-aware IntelliSense, guardrails for risky statements and clear error messages, for Oracle and the other databases you use.