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


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

Cause: The archiver process received an error while trying to archive a redolog. 
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.

Action: Check the archiver trace file for a detailed description of the problem.
Also, verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST 
is set up properly for archiving.

ORA-00257 comes under "Oracle Database Server Messages". 
These messages are generated by the Oracle database server when running any Oracle program.
How to free archive destination device:
Most probably archive destination is full. We should backup archive logs, then remove them.

We can use following steps for this
1. find the location of Archive destination by
 show parameter archive_dest
 
 lets say it provide  LOCATION=/u10/oradata/mydb/arch

2. move some files to some other location using os command
 cd /u10/oradata/mydb/arch
 mv /u10/oradata/mydb/arch/* /u15/oradata/mydb/arch-bkp/
 

Or it can be done using RMAN also

rman target /

RMAN> backup archive log all format '/u15/oradata/mydb/arch-bkp';

RMAN> delete archive until time 'trunc(sysdate)';

Related Posts:
- ORA-04031: unable to allocate n bytes of shared memory
- ORA-01157: cannot identify/lock data file string - see DBWR trace file
- ORA-00849: SGA_TARGET cannot be set to more than MEMORY_MAX_TARGET
- ORA-27101: shared memory realm does not exist
- ORA-00604: error occurred at recursive SQL level string
- ORA-00600: internal error code
- ORA-16000: database open for read-only access
Labels:

12 comments:

  1. Mona JhaJanuary 23, 2012 at 9:49 PM

    Nyc one..

    ReplyDelete
  2. ranvir meshramJanuary 23, 2012 at 9:51 PM

    You do like this also, as follows;

    rman
    RMAN> connect target sys/password@DBname

    DELETE NOPROMPT ARCHIVELOG UNTIL TIME "SYSDATE-5"


    run {
    allocate channel t1 type disk;
    backup current controlfile format '/u01/ora_backup/rman/%d_%u_%s';
    backup database format '/u01/ora_backup/rman/%d_%u_%s';
    sql "alter system archive log current";
    backup archivelog all delete input format '/u01/ora_backup/rman/arch_%d_%u_%s';
    release channel t1;
    }


    Ranvir here...
    ranvir.meshram@gmail.com

    ReplyDelete
  3. ranvir meshramJanuary 23, 2012 at 9:55 PM

    Find out file system usage for Oracle archive destination using OS command:

    $ df -k | grep oraarch

    Ranvir here...

    ReplyDelete
  4. Ajay Kumar BaranwalJanuary 24, 2012 at 3:50 PM

    Good work, very informative, keep it up

    ReplyDelete
    Replies
    1. Nimish GargAugust 9, 2012 at 11:08 PM

      Thanks Ajay, you must check out Oracle SQL, Oracle PL/SQL and Oracle Tips

      Delete
  5. Nimish GargJanuary 24, 2012 at 3:54 PM

    This comment has been removed by the author.

    ReplyDelete
  6. UnknownMay 21, 2013 at 11:45 AM

    Dear Nimish when i connect the system/system@string then same error is showing (ora-00257),how to solve ?

    ReplyDelete
  7. UnknownDecember 8, 2016 at 6:35 PM

    Good detail

    ReplyDelete
  8. pg slotFebruary 9, 2024 at 5:57 PM

    pgสล็อต สล็อตออนไลน์ เว็บตรง แตกง่าย จุดเริ่มของพวกเรานั้นพวกเราก็จำเป็นต้องขอย้อนไปในช่วงเวลาที่พวกเรานั้นยังปฏิบัติงานประจำอยู่เลย pg slot ช่วยให้ท่านได้สนุกไปกับเรา

    ReplyDelete

Subscribe to: Post Comments (Atom)