• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1801
  • Last Modified:

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

I am having an ORA-00257 error when trying to connect to oracle

Can anyone share what all scenarios cause this problem and how we can fix it.I t would be fine if i get multiple fixes for this error..i.e multi scenarios which cause issues.

How to archive set up properly check .

I am using 10gR2 database on OS CentOS 4.4.  what and how to set up archive properly?? the archive file can get huge.

1 Solution
Haris DjulicCommented:
check the disk space ...

this is usually error when disk used by oracle is full..

you should change location for you archive logs to be somewhere else or move them to another server ...
Richard OlutolaConsultantCommented:
If you use RMAN to backup, it can manage your archivelogs for you so your disks don't get filled up.

RMAN> backup database plus archivelogs delete input;

This will do a full backup of the database and the arvhivelogs, and delete backed up archivelogs.

couple of immediate options
1 if you dont want the archive logs delete them  using os command eg rm ....
and log in to the database as sys "/ as sysdba"
alter system switch logfile;

2 move the archive logs from the current position to another mountpoint
create a soft link  in the current location so that when you backup rman can read them using the soft link.
log in to the database as sys "/ as sysdba"
alter system switch logfile;

run the backup.

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

immediately, you should make some space in the archive location so that problem will go and once you have some space in archive location, do a "alter system switch logfile". you can make space, by moving the old archives to other directories, taking the backup and removing or, if you have already backed them up then just remove it using RMAN with command "backup archivelog all delete input"
or " delete archivelog all completed before 'sysdate-1'; it depends, how much archives you want to retain on this archive location.
Mark GeerlingsDatabase AdministratorCommented:
Basically, you need to manage the archived redo logs so this situation doesn't happen again.  You can either use RMAN to delete the ones you don't need, or use an O/S script to either compress then and/or move the older ones to a different disk.

What kind of backup strategy do you have now?  Do you use RMAN, or something else?
Pradeep_TiwariAuthor Commented:
I am using RMAN backup with 10gR2 database
Richard OlutolaConsultantCommented:
What I do on my development environment where many archivelogs can be generated each day is to run a scipt every night which backs up the archivelogs and deletes them with RMAN>backup archivelog all delete input;

This frees up the archivelog location ready for the next day.

If you take COLD backups nightly, then you simply need to delete the archivelogs and crosscheck them so that RMAN removes them from its repository.

Let me know if you require any further info.

Pradeep_TiwariAuthor Commented:
problem is solved

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now