Re: physical standby WAIT_FOR_GAP
Date: Tue, 22 Dec 2009 14:30:08 -0500
Message-ID: <ae2c46ba0912221130y563ba127lca4e0e28f4089239_at_mail.gmail.com>
As far as I understand, you can't skip logs on a physical standby. What always works for us in this case is to just RMAN restore the missing archivelog(s) back to its original destination on the primary. Once the archivelog has been restored, dataguard will automatically sense that its there and ship it over. Dataguard works quite nicely in this respect(and many others).
On Tue, Dec 22, 2009 at 2:26 PM, Li Li <litanli_at_gmail.com> wrote:
> Greetings List,
>
> We have a physical standby running on a 4-node RAC. last night the
> apply instance (instance 1) had ora-04031 error and data guard broker
> changed the apply instance to be instance 2. Now apply instance
> (instance 2) shows "WAIT_FOR_GAP" for a log sequence 5xxx, which is a
> very old log, and has been applied a long time ago. Has any one seen
> this before? How do I trick the apply instance to skip the logs that
> have been applied already and start applying the logs that haven't
> been received but haven't applied.
>
> Oracle version 10.2.0.3 on RHEL AS 4.7
>
> Thanks and hope you all a merry christmas and happy new year!
> -Li
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Dec 22 2009 - 13:30:08 CST