Re: RMAN/DG - delete *ONLY* archive logs "already shipped to thestandby DataGuard database"?

  • From: Steven Patenaude <spatenau@xxxxxxxxx>
  • To: joelgarry@xxxxxxxxxxxxxxx
  • Date: Tue, 11 Jan 2005 17:32:34 -0600

On Tue, 11 Jan 2005 14:04:14 -0800, Joel Garry
<joelgarry@xxxxxxxxxxxxxxx> wrote:
> Marquez, Chris wrote:
> >BUT delete *ONLY* archive logs "already shipped to the standby
> DataGuard
> >database".
> Sure you want to do that?  What if it can't apply logs already shipped?
> When you write your own script, be sure to put in some slop so you don't
> delete too many, or else some intelligence so you only delete those that
> have been applied and shown to work, as exemplified by being able to
> open R/O the standby.

Do you think he'll need slop if instead of checking for "shipped" he
checks for "applied"?  The standby shouldn't mark that log as applied
if it finds the log to be corrupt.  That is, given a corrupt archive
log, either the standby will detect the local archive log as corrupt
and not apply it (and so RMAN won't delete the original), or the
standby will not detect it as corrupt and he's in a whole new world of
hurt anyway.  In the first case, he'll be able to ship over a new,
uncorrupted copy (assuming the original isn't corrupted).  In the
second case, well, that archive log probably won't be needed because
he's rebuilding the standby anyway.

I guess what I'm asking is, given this statement:
> Thanks to various bugs I've run into in 8i/early 9, I habitually keep
> days worth of archives after rman/backup.  One just never knows what
have you needed an archive log after it has been accepted and applied
to the standby?  If so, I'd like to know about it to guard against
this scenario in the future.


Other related posts: