Re: Standby database and skipping lost Archive Redo Log

Unless you start getting seriously clever with hex-editing the headers of the archived logs, and fooling the standby database into thinking that the missing log(s) have returned, then the answer is that, no, you can't skip redo.

I have heard of one case where copies of archives were indeed edited to look like the old ones, but I haven't got a clue how it would be done, wouldn't recommend it even if I did, and Oracle Support would probably declare that henceforth you were on your own.

I'd say a re-initialisation was your best bet... and a change to your backup strategy such that archives are left lying around for a good deal longer than 48 hours. Given that three day weekends are not exactly rare, I'd propose you up that time limit to 72 hours minimum., and 5 days would be better. It's only storage space, after all, versus potential data loss.

Regards
HJR <kkarns8565_at_my-deja.com> wrote in message news:94b9fk$u0o$1_at_nnrp1.deja.com...
> We're running Oracle 8.1.6.1.1 on a pair of SunOS 5.7 boxes in a
> standby architecture.
>
> Can anyone tell me if it is possible to make a standby database skip an
> Archive Redo Log?
>
> This past three day weekend I found out that a 'hiccup' on our standby
> database early Friday
> evening went undetected until Tuesday. Because we didn't change the
> tapes out on Monday,
> (Boy, would an autochanger be nice!) and because our backup procedure
> purges Archive Redo Logs
> after 48 hours we found ourselves without an Archive Redo Log that we
> needed on the standby
> server.
>
> Is there an easy way to make the standby database skip this particular
> log file file, or will I
> be forced to re-initialize the standby database in order to get things
> back in sync? I happen
> to know that there are no transactions in this log file that are
> important.
>
>
> Sent via Deja.com
> http://www.deja.com/
Received on Sat Jan 20 2001 - 01:27:08 CST