Re: Block Change Tracking at Switchover - Version Dependency?
Date: Tue, 11 Aug 2020 10:29:37 +0100
Message-ID: <CAA0QMt=G9WqWQjOyS+V1eRNsBcTzQKEex1JAp0GMoyqos-SVMw_at_mail.gmail.com>
Hello,
I cannot find any defitive documentation on how its supposed to work in 11g, just the new features documentation.
I vaguely remember we had a very bad bug with BCT on the standby that prevented the primary from working at all so we put a manual step into our failover/switchover documentation.
If you want certainty it would be worthwhile logging an SR.
Regards,
Frank
On Fri, Aug 7, 2020 at 4:23 PM Charlotte Hammond < dmarc-noreply_at_freelists.org> wrote:
>
> Hello
>
> I'm looking for a quick sanity check on Block Change Tracking behavior on
> switchover.
>
> In our setup we don't have ADG so we only intend to have BCT on the
> primary.
>
> On 11g databases this seems to be a manual process. If we do nothing the
> BCT remains enabled on the old standby and disabled on the new primary (not
> what we want - so we have to manually disable/enable accordingly).
>
> On 18c databases this seems to automatically follow the switchover. The
> BCT is automatically disabled on the old standby and automatically enabled
> on the new primary.
>
> I can't find this in the documentation. Is somebody able to point me in
> the right direction please?
> I don't want to just rely on the above experimentation as there are
> obviously costly licence implications so want to be sure I understand what
> is meant to be happening in both cases.
>
> Thank You!
>
> Charlotte
>
-- +353-86-0695383 -- http://www.freelists.org/webpage/oracle-lReceived on Tue Aug 11 2020 - 11:29:37 CEST