Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Backup toubles: How and when can I delete my archive logs?
Comment below.
-- ---------------------------------------------- Resources for Oracle: http://www.hjrdba.com =============================== "Jeff" <jeff_at_work.com> wrote in message news:a5nvek$729$1_at_cronkite.cc.uga.edu...Received on Fri Mar 01 2002 - 11:35:25 CST
> In article <a5m6jq$p7s$1_at_lust.ihug.co.nz>, "Howard J. Rogers"
<dba_at_hjrdba.com> wrote:
> >Two things. It's utterly pointless taking the thing in and out of
> >archivelog mode. What's the point? You're trying, I presume, to ensure
> >that your archive sets are as up to date as they can possibly be. Why?
> >What you don't backup today, you'll backup tomorrow.
>
> Uh, he's not exactly taking it in and out of archivelog mode (you can't do
> that with an opened database anyway). He's just stopping the archiver
> temporarily while he copies off the existing archived logs and does a mass
> delete on the archive directory. It'd be bad if he happened to delete a
new
> archived log that didn't get copied off. Probably an extreme long shot on
> that happening, but still a possibility that should be accounted for.
> Murphy's Law applies.
>
True enough, and I was careless in my choice of terminology -but switching of ARCH is equally pointless. If you (or he!) were to base your decision on what to delete on v$archived_log, the question of a 'hot delete' wouldn't arise. Meanwhile, being in archivelog mode with ARCH switched off is just asking for a system hang. Regards HJR
>
> >Second, why on earth are you restoring controlfiles? There is only one
>
> Yeah, this is probably what's causing his "backup troubles."
>
>
> >the start of your backup cycle). Nevertheless, it pays to keep at least
2
> >or 3 days of archives available... I can show you posts from here where
> >people have discovered that they've been backing up corrupt datafiles for
a
> >week, and need to restore from much further back than they ever
anticipated.
>
> That is always good advice... but I got the impression that he'd intended
to
> keep older logs anyway... just that he didn't understand why Oracle was
still
> asking for them after restoring and recovering a more recent backup.
![]() |
![]() |