Re: ORA-00257 archiver error. connect internal only, until freed. Well, how can I securely "freed"

it created one flash recovery area file couple hours ago, alert log does not say anything, last message was:

Severity=Unreachable Clear
Message=Agent Unreachability is cleared. The current status of the target is UP.
Rule Name=Database Availability and Critical States Rule Owner=SYSMAN

I read somewhere that once make full backup with rman, all archivelogs can be removed. After reading more about rman, and still being confused with number of options and switches it got, I dont think that the above is even a question.

I am just trying to get to the point where my ora10gR2 is backed up fully (everything) and I dont have to worry about it (old archives are removed from disk device). I have 50gb partition for that logs and backups. My tablespace is 200mb, archive logs about 50 mb each about 250 mb a day.
What would be the likely best settings for backup? should one backup each day just controlfile and datafiles, and keep archivelogs until that backup happened and then remove them, or also back them up (what is the reason for that?)

On Jun 9, 4:39 pm, Charles Hooper <hooperc2..._at_yahoo.com> wrote:
> On Jun 9, 12:53 pm, sybra..._at_hccnet.nl wrote:
>
>
>
>
>
> > On Sat, 09 Jun 2007 09:04:46 -0700, Joe <joe1..._at_tlen.pl> wrote:
> > >I would like to backup entire system: control files, archive logs,
> > >datafile copy, basically - everything in order to get zero problems
> > >putting ora online after major crash.
> > >should one (ccording to my show all settings) use the following
> > >command:
>
> > >RMAN> BACKUP ARCHIVELOG ALL DELETE ALL INPUT;
>
> > >is there anything this command is not backing up?
>
> > It is *only* backing up the archivelogs, it is NOT backing up the
> > database etc.
>
> > --
> > Sybrand Bakker
> > Senior Oracle DBA
>
> That could make it difficult for the OP to recover from problems. The
> 10g R2 Enterprise Manager Database Control makes it easy to set up
> RMAN so that it backs up the database, archived redo log files, and
> control file, while keeping X number of database backups in the flash
> recovery area. It is a good idea to force log file switches
> occasionally, for instance every 30 or 60 minutes.
>
> If no new archived redo logs are making it into the flash recovery
> area, check the Alert log to determine if the database instance still
> believes that the flash recovery area is full.
>
> Charles Hooper
> IT Manager/Oracle DBA
> K&M Machine-Fabricating, Inc.- Hide quoted text -
>
> - Show quoted text -
Received on Sat Jun 09 2007 - 16:33:42 CDT