Re: Data Guard gap discrepancy?

From: Niall Litchfield <niall.litchfield_at_gmail.com>
Date: Thu, 7 Apr 2016 09:23:46 +0100
Message-ID: <CABe10sbG48YQa2Vwnw0bgPkcwa=y4w_FVijiDdOX79y8hue-Yw_at_mail.gmail.com>

In a word yes.
https://docs.oracle.com/cloud/latest/db121/REFRN/refrn30009.htm#REFRN30009 LOW_SEQUENCE# is that last *received* log on the standby.

On Thu, Apr 7, 2016 at 5:31 AM, Rich J <rjoralist3_at_society.servebeer.com> wrote:

> Hey all,
>
> I have an active data guard setup in 11.2.0.3 with a non-RAC primary and a
> single physical (open for read) standby.
>
> For fun maintenance-related reasons tonight, I managed to have a gap in
> the shipped logs. V$ARCHIVE_GAP said the low sequence was 57645, so I
> started manually restoring logs from there. But when I checked
> V$MANAGED_STANDBY, it said MRP0 was in WAIT_FOR_GAP on sequence 57646. I
> did have an "ORA-01153: an incompatible media recovery is active" starting
> MRP with archived log sequence 57645 manually restored, if that matters (a
> restart of the MRP cleared that up). Once the restored logs were registered
> on the standby, MRP was happily on its merry way.
>
> So, am I misreading the meaning of the "LOW_SEQUENCE#" column in
> V$ARCHIVE_GAP?
>
> Thanks!
> Rich
>

-- 
Niall Litchfield
Oracle DBA
http://www.orawin.info

--
http://www.freelists.org/webpage/oracle-l

Received on Thu Apr 07 2016 - 10:23:46 CEST