Re: Flashback guaranteed restore point with ADG for DB upgrade fallback

I think you alluded to this Rich but enabling Flashback Database is not required for GRPs but I haven't tested it on a standby database.

Seth

On Wed, Oct 10, 2018 at 3:39 PM Rich J <rjoralist3_at_society.servebeer.com> wrote:

> On 2018/10/10 13:11, Jose Rodriguez wrote:
>
> I've recently used the exact same approach for an ADG upgrade. This was
> 11.2.0.3 to 11.2.0.4, but the idea is the same.
> As Niall says, just enable flashback database on both sides, create a GRP
> on the standby first and then on the primary, so you have an older SCN on
> the standby in case of a rollback.
> Bear in mind the required FRA space for the flashback logs, not much for
> the upgrade itself, but this will be recording the applied redo on the
> standby as well if I recall correctly.
> I tested it and it worked like a charm.
> I am not at my desk right now, so I can't share any docs, but I'll take a
> look tomorrow.
>
> I'm testing this now, and have gotten further than I did before, but am
> getting ORA-19909 starting MRP on the standby. Looking at V$INSTANCE, the
> instance_role is "PRIMARY_INSTANCE". It appears someone forgot to use the
> "STANDBY" keyword when doing the flashback. Doh. At least that sounds
> like it could be the cause.
>
> I don't want to spend the amount of time it would take to properly test
> the effects of enabling flashback on the databases, which appears to be
> necessary to flashback to an SCN on the standby. Creating a guaranteed
> restore point on the standby seems to be the way to go here, as Oracle
> allowed it, even if I...erm, "someone"...forgot the proper keyword.
>
> More testing tomorrow -- thanks all for the replies!
>
> Rich
>

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