Re: physical standby WAIT_FOR_GAP
Date: Tue, 22 Dec 2009 14:09:03 -0600
Message-ID: <5f35c2320912221209h61d52dd9pbc9fd9ba1753891d_at_mail.gmail.com>
Hi, Jason,
We are using ASM on both primary and standby. so what I need to do is:
- backup current controlfile for standby on primary side
- copy the backup controlfile to standby side
- restore the controlfile on standby side
Is that what you did to resolve this issue?
Thank you very much for your time!
-Li
On Tue, Dec 22, 2009 at 1:46 PM, jason arneil <jason.arneil_at_gmail.com> wrote:
> Hello,
>
> I've seen this scenario occur quite a bit as well. I've seen creating
> a new standby controlfile from the primary can straighten things out.
>
>
> jason.
>
> --
> http://jarneil.wordpress.com
>
>
>
> 2009/12/22 Li Li <litanli_at_gmail.com>:
>> 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 - 14:09:03 CST