Prerequisites

1 Prerequisites

Following are the prerequisites for using Oracle GoldenGate on Oracle Cloud Marketplace.

Supported Browsers

Oracle Cloud Infrastructure supports the latest desktop versions of Google Chrome, Microsoft Edge, Safari, Firefox, and Firefox ESR.

Note that Mobile browsers as well as private browsing mode is not supported for Firefox or Edge.

Prerequisites to Deploy Oracle GoldenGate Microservices

Here are the prerequisites required to deploy Oracle GoldenGate Microservices:

Oracle Cloud Account
Access to assigned Oracle Cloud Tenant
Compute node resources within Oracle Cloud Tenant
Local SSH/RSA Key

Create an SSH/RSA Key

To work with the Oracle Cloud Infrastructure once the Oracle GoldenGate Compute Node is built, you have to provide a SSH Public Key during the interview process that will allow you to log in to the node once built.

Perform the following steps to build your SSH keys:

Open a Terminal window and start the key generation program by typing the following command:
```
$ ssh-keygen Generating public/private rsa key pair.
```
Enter the path to store this file. By default, this gets saved in your home directory under a hidden folder called.ssh. Change this default location, if required.
```
Enter file in which to save the key (/Users/johndoe/.ssh/id_rsa): <Return>
```
Enter a passphrase for using your key.
```
Enter passphrase (empty for no passphrase): <passphrase>
```
Re-enter the passphrase to confirm it.
```
Enter same passphrase again: <passphrase>
```
Check the results.
The key fingerprint (a colon separated series of 2 digit hexadecimal values) is displayed. Check if the path to the key is correct. In the above example, the path is /Users/johndoe/.ssh/id_rsa.pub. You have now created a public or private key pair.

Note:

For generating key pair on Windows platform, refer to Creating a Key Pair section in Oracle Cloud Infrastructure Documentation.

OCI Policies Needed for Creating Oracle GoldenGate Marketplace Instances

The following OCI policies are required for creating Oracle GoldenGate Market Place instances:

Allow group <ggowner> to manage instance-family in compartment <Compartment Name>
Allow group <ggowner> to manage orm-family in compartment <Compartment Name>
Allow group <ggowner> to manage volume-family in compartment <Compartment Name>
Allow group <ggowner> to use virtual-network-family in compartment <Compartment Name>
Allow group <ggowner> to manage public-ips in compartment <Compartment Name>
Allow group <ggowner> to use tag-namespaces in tenancy
Allow group <ggowner> to inspect compartments in tenancy

Where <ggowner> is an example for a group and <Compartment Name> is an example of a compartment. The following are permission names: instance-family, orm-family, volume-family, virtual-network-family, and public-ips.

Note:

The manage public-ips permission is required only if you give the instance a public IP address. Oracle GoldenGate uses reserved IP addresses so that the public address is preserved across stack upgrades.
The Networks compartment is an assumption that the customers follow the practice of having a separate network group manage the network resources for all users in the tenancy. If the tenancy instead allows you to create network resources of your own, then the policy would be: Allow group <marketplace-permissions> to manage virtual-network-family in compartment <Marketplace-Test>.

Configuring Source or Target Database for Replication

Before you can begin replicating data, you should prepare the source or target database to support Oracle GoldenGate. For more information about steps to prepare your Oracle database, see Configure Databases and view details for the relevant database in Oracle GoldenGate Microservices Documentation.

Cross Cloud Functionality

Oracle GoldenGate is designed for large scale, cloud based architectures and Oracle GoldenGate on Oracle Cloud Marketplace is a key to many cloud-based solutions. By using Oracle GoldenGate from the Oracle Cloud Marketplace, you can replicate data from on premise to the Oracle Cloud, between data points within the Oracle Cloud, or even between third party clouds.

Network Recommendations

The network recommendations listed here primarily apply for Oracle to Oracle replication, but the general rules apply to all platforms supported by Oracle GoldenGate. This applies to Oracle GoldenGate on-premise, in 3rd party clouds, in the Oracle cloud, and OCI GoldenGate.

For Capture: Network latency is critical for performance throughput of an Extract and it is recommended to ensure that the Marketplace deployment is in the same region, or as close as possible, to the database server.
For Replicat: If you run Oracle GoldenGate remotely (on a separate server from the database that Oracle GoldenGate is applying changes to) then the round trip ping time must be less than 5ms.
For Oracle GoldenGate to Oracle GoldenGate communication: The Oracle GoldenGate trail files grows at about 30-40% of the generated redo log volume (if you are capturing 100% of the data). That means that Oracle GoldenGate sends about 30-40% of the generated redo log volume across the network. If the network is not able to scale to this volume, then you can enable compression on the trail file data being sent across the network. This compression can typically achieve 8:1 compression ratios or better. You can also modify the TCP window socket size and buffers as well.

The following table provides a matrix on cross cloud support for replication by using Oracle GoldenGate on the Oracle Cloud Marketplace:

Table 1-1 Oracle GoldenGate Cross-Cloud Support

Technology	Remote Capture	Remote Apply
Oracle Cloud Infrastructure	Yes	Yes
Amazon Web Services (AWS)	Yes	Yes
Microsoft Azure	Yes	Yes
Google Cloud Service	Yes	Yes