ORA-00257 SQL Origin: Data OSI layer 7 · Application Last updated 18 Nov 2026

ORA-00257: archiver error. Connect internal only, until freed

The archive log destination is full, so the database can't archive redo logs and blocks work.

Exact message you may see ORA-00257: archiver error. Connect internal only, until freedArchiver error. Connect AS SYSDBA only, until freedarchive log destination full OracleORA-16038 log cannot be archived
Seen on: Oracle Linux

Meaning

Free space in the archive destination or the Fast Recovery Area: delete obsolete archive logs with RMAN (DELETE ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE-1' after backup), increase db_recovery_file_dest_size, and fix the backup job that normally removes them.

Common causes

  • Archive destination or FRA full
  • RMAN backups failing so logs aren't deleted
  • db_recovery_file_dest_size too small
  • Heavy redo generation
  • Disk full

⚡ Quick fix

  1. Check v$recovery_file_dest usage
  2. Back up and delete archived logs with RMAN
  3. Increase the FRA size or disk

Detailed fix by platform

SQL

  1. sql
    SELECT space_limit/1024/1024 mb_limit, space_used/1024/1024 mb_used FROM v$recovery_file_dest;
    RMAN> DELETE NOPROMPT ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE-1';

How to diagnose

  1. FRA — Full?
  2. RMAN — Backing up?
  3. Redo — Spiking?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Data. Errors that are often confused with or caused by this one (click to open):

9002 — SQL Server Error 9002: The transaction log for database is full (SQL)9002ORA-00001 — ORA-00001: unique constraint (SCHEMA.PK_X) violated (SQL)ORA-00001ORA-00018 — ORA-00018: maximum number of sessions exceeded (SQL)ORA-00018ORA-00020 — ORA-00020: maximum number of processes (150) exceeded (SQL)ORA-00020ORA-00028 — ORA-00028: your session has been killed (SQL)ORA-00028ORA-01034 — ORA-01034: ORACLE not available (ORA-27101: shared memory realm does not exist) (SQL)ORA-01034ORA-01652 — ORA-01652: unable to extend temp segment by 128 in tablespace TEMP (SQL)ORA-01652ORA-00257

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.