Adding to Seth’s suggestion, consider using DBFS, and install GG on it, and you
will never have to worry about it. It is a neat way for filesystem replication,
and *not* buggy(compared to ACFS).
Disclaimer: The information transmitted is intended for the person or entity to
which it is addressed and may contain confidential, privileged or copyrighted
material or attorney work product. If you receive this in error, please contact
the sender and delete the material from any system. Any unauthorised copying,
disclosure or distribution of the material in this e-mail is strictly
forbidden. Any comments or statements made are not necessarily those of
Fidelity. All e-mails may be monitored or recorded.
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Seth Miller
Sent: 12 February 2020 23:58
Cc: sbecker6925@xxxxxxxxx; oracle-l <oracle-l@xxxxxxxxxxxxx>
Subject: Re: Installing GoldenGate on standby server
If you want GG to work properly in the event of a switchover/failover, it
should be tied into the clusters using XAG.
On Tue, Feb 11, 2020 at 3:44 PM Reen, Elizabeth
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.
<oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>> On Behalf
Of [External] Sandra Becker
Sent: Thursday, February 6, 2020 12:19 PM
Subject: Installing GoldenGate on standby server
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
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