Re: Loss of Both current redo logs

I always set up mirrored redo log groups across different disks so that no one redo log file is a single point of failure.

Flora Seymour wrote:

> Hi
>
> I have a question on the loss of current REDO log files and recovery that I am
> hoping someone might like to comment on.
>
> It is my understanding that if we were to lose both current redo log files that
> we would have to restore our database and recover up to just before the
> creation of those lost redo logs.
>
> For us this could mean the loss of allot of critical data. Here is why...
>
> We have fairly large redo log files (100m) to prevent frequent switching
> during our nightly batch processing that does a lot of large updates. This
> means that during our online day, where we have *alot* of small update
> transactions (customer requests), our log files do not switch at all. This
> implies that if we were to loss both current redo logs near the end of our
> online day we would loss all transactions for that day (we have no paper trail
> - no way to re-create these transactions). I am thinking that we should
> schedule a job to run every 15 minutes or so during our online day that would
> force a switch of our redo logs. That way, if we were to be so unlucky that we
> lost both of our online redo logs (yes they are on different disks and
> controllers), we not lose allot.
>
> What negative side effects would forcing a switch every 15 minutes imply? Is
> this a bad idea? Am I understand this correctly? Am I overly paranoid?
>
>
> Thanks in Advance for any input...
> Flora
Received on Mon Jul 20 1998 - 16:39:02 CDT