- Does Oracle GoldenGate support the remote capture and delivery for the source and target databases? (Yes)
- Do you have a high standard on the replication throughput and latency? (No)
- Do you need Oracle GoldenGate to fail-over with Active Data Guard on the capture side? (No)
- Do your source/target databases' operating systems have the same endian as the hub? (Yes)
The following discussion provides some details on each question.
1.1. Does Oracle GoldenGate support the remote capture and delivery for the source and target databases? (Yes)
To answer this question, you need to know the source and target database types/versions, and the version of the Oracle GoldenGate running on the hub:
- The source/target databases: For some databases, such as MySQL and DB2 for i, Oracle GoldenGate doesn't support remote capture. Then, you have to install Oracle GoldenGate on the database server to perform the replications.
- The Oracle GoldenGate version: Some Oracle GoldenGate versions don't support the remote capture and delivery. For example, Oracle GoldenGate 12.2 doesn't support the remote capture and delivery for DB2 z/OS. However, Oracle GoldenGate 12.3 supports it. You then have to either install Oracle GoldenGate 12.2 on the database server or run Oracle GoldenGate 12.3 on a hub for your replication.
1.2. Do you have a high standard on the replication throughput and latency? (No)
Due to the network communications, the remote capture and delivery, in general, has 15-20% downgrade from the native implementation. Note that this is an unofficial number, you need to test in your environment when evaluating the solution. In other words, if you do have high standard on the replication throughput and performance, then you would need to run some performance tests with the remote capture and delivery before making the decision.
1.3. Do you need Oracle GoldenGate to fail-over with Active Data Guard on the capture side? (No)
To enabling Oracle GoldenGate to fail-over with Active Data Guard, you have to install Oracle GoldenGate on the database server and within the DBFS files system [1].
1.4. Do your source/target databases' operating systems have the same endian as the hub? (Yes)
The server running Oracle GoldenGate and the server running the database or database server have to have the same Endianness. Please refer to Endianness and the Operating System [2] for more information.
2. Case Studies
Let's look at some examples.
Example 1: I'd like to migration an on-prem Oracle 9i database to an on-prem Oracle 12c database. Can I use GGCS with the remote capture and delivery?
Answer: No. This is because GGCS runs on Oracle GoldenGate 12.2 which doesn't support Oracle 9i. You have to install an old build of Oracle GoldenGate to replicate Oracle 9i database. GGCS can be used for the on-prem Oracle 12c database.
Example 2: I'd like to set up a replication from an DB2 for z/OS database on-premises to an Oracle Database Cloud Service. Can I use GGCS to perform the remote capture and delivery?
Answer: No. This is because GGCS runs on 12.2 doesn't support remote capture from the DB2 for z/OS database. After GGCS is upgraded to Oracle GoldenGate 12.3, then you can use GGCS to remotely capture from DB2 for z/OS. Now, GoldenGate on-prem has to be used to replicate the DB2 for z/OS database.
Example 3: I'd like to setup a one-way replicate between Oracle 12c Database hosted on Amazon AWS. Can I use GGCS with the remote capture and delivery?
Answer: Yes, you would need to have a secure SQL*Net connection to the databases on AWS and the privileges to perform database configurations for the Oracle GoldenGate replication.
Remote capture and delivery architecture has benefits, but you would evaluate it carefully to make sure it meets your needs.
- Oracle Technical Whitepaper, Transparent Role Transitions With Oracle Data Guard and Oracle GoldenGate, February 2015