Re: Installing GoldenGate on standby server

From: Seth Miller <sethmiller.sm_at_gmail.com>
Date: Wed, 12 Feb 2020 12:27:54 -0600
Message-ID: <CAEueRAWtaGXgfmQ34z19wJu1cUxQUw7Zgb3Tn3u1RR1NDnanCA_at_mail.gmail.com>



Sandra,

If you want GG to work properly in the event of a switchover/failover, it should be tied into the clusters using XAG. https://www.oracle.com/technetwork/database/availability/con6570-availabilityggmicroservices-3960454.pdf

Seth

On Tue, Feb 11, 2020 at 3:44 PM Reen, Elizabeth <dmarc-noreply_at_freelists.org> wrote:

> The standby GG will not know where the production GG left
> off. The easiest way out of the problem is to have a third server run the
> GG.
>
>
>
>
>
> Liz
>
>
>
> *From:* [External] oracle-l-bounce_at_freelists.org <
> oracle-l-bounce_at_freelists.org> *On Behalf Of *[External] Sandra Becker
> *Sent:* Thursday, February 6, 2020 12:19 PM
> *To:* oracle-l
> *Subject:* Installing GoldenGate on standby server
>
>
>
> Oracle EE12.1.0.2
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__12.1.0.2&d=DwQFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=yWMFosURAngbt8VLeJtKLVJGefQxustAZ9UxecV7xpc&m=l_Z3Ar8mzckb948Rt9wMjBslZHQXg-VP_9H9c6huufk&s=nK00B0vn5wpJgY3_s9lSAGEfLe9B7Aq_oL6vTFLt4Us&e=>
>
> GoldenGate 12.2.0.1
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__12.2.0.1&d=DwQFaQ&c=j-EkbjBYwkAB4f8ZbVn1Fw&r=yWMFosURAngbt8VLeJtKLVJGefQxustAZ9UxecV7xpc&m=l_Z3Ar8mzckb948Rt9wMjBslZHQXg-VP_9H9c6huufk&s=9TnR7qHSGcVkfMNqLdv2u4ZqvL9SxA0nZi96U7Zr5c8&e=>
>
>
>
> I'm fairly new to supporting GoldenGate and all the DBAs who used to do it
> are no longer at the company. We also lack good documentation, which I am
> working to rectify. We are preparing to move a production database to a
> new servers & storage that will have a primary and a standby vs the single
> instance we have now. We currently use GoldenGate to replicate data from
> several tables to another database on another server. I don't want to be
> in the position of needing to install GG on the standby server in the event
> we need to switchover/failover and cause delays in the replication to the
> other database. From what I've read, I can install it, but not start it on
> the standby server so it will be ready in the event we need it. By design,
> the primary and standby servers will not share anything. If you have a
> moment, please review the steps I think I need and let me know if this will
> work or if I've missed anything.
>
>
>
> 1. Download the same version of GG to the standby that the primary is
> running
> 2. Run the installer
> 3. Do *not* check "Start manager" during the install *or *check "Start
> Manager" and stop it after the installation (not sure which is the better
> way to go)
> 4. Copy the parameter files from the primary to the standby
> 5. Update the team documentation to note that any changes to the
> primary must also be done on the standby
>
>
> --
>
> Sandy B.
>

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Feb 12 2020 - 19:27:54 CET

Original text of this message