Deploy Oracle GoldenGate Maximum Availability Hub on Oracle Cloud Marketplace

After you find Oracle GoldenGate Maximum Availability Hub on Oracle Cloud Marketplace, you can deploy it using the provided Stack Listing. This TerraForm Stack prompts you for specific information and then builds the Oracle Cloud Infrastructure Compute Nodes with the desired hardware settings, configures the desired network settings, and starts the Grid Infrastructure and Oracle GoldenGate installations.

Before you begin

Ensure that you add all required policies before you proceed.
You have the option to create a new Virtual Cloud Network (VCN) or using an existing one. If using an existing VCN, ensure that the network configuration meets the requirements as documented in Create a custom Virtual Cloud Network (VCN).

Note:

Customizations to the stack settings are not kept intact when you upgrade the stack. Carefully consider whether customization is necessary, and ensure that you take note of custom settings so that you can reapply them after upgrading.

To deploy Oracle GoldenGate Maximum Availability Hub on Oracle Cloud Marketplace using the Stack Listing:

On the Oracle GoldenGate Maximum Availability Hub Application page, select Get App.
Select Commercial Market or Government Market, and then click Sign In.
Enter the tenancy name for Cloud Account Name, and then click Next.
Sign in to the Identity provider.
On the Oracle GoldenGate application page, provide the following information, and then click Launch Stack:
- Select Version - It provides a list of available versions for the listing.
- Select Compartment - Specifies the compartment where the compute node will be built. It is generally the location that you have access to build the compute node.
- Terms of Use - Review the Oracle standard Terms and Restrictions, and then select the checkbox.
Fill in the required Stack information:
- Name - Name of the Stack. It has a default name and provides a date time stamp. You can edit this detail, if required.
- Description - Description of the Stack that you are creating.
- Create In Compartment – It defaults to the compartment you have selected on the Oracle GoldenGate application page.
- Tags (optional) – Tags are a convenient way to assign a tracking mechanism but are not mandatory. You can assign a tag of your choice for easy tracking. You have to assign a tag for some environments for cost analysis purposes.
- Click Next.
Fill in the required details to configure variables. This information is required to build the cluster compute nodes with for Oracle GoldenGate Maximum Availability Hub.
1. For Name for New Resources, enter:
  1. Cluster Prefix: The prefix to identify the cluster.
    Note:
    This prefix must be unique within the Compartment and meet the following requirements:
    
    At least 1, but no more than 14 characters in length.
    
    Contains only single-byte alphanumeric characters (upper or lowercase) or hyphens (-).
    
    Must begin with a letter.
    
    Can't start or end with a hyphen.
  2. Hostname Prefix: The prefix to identify an instance in the cluster. You can change the default prefix, but it must be between 2 and 8 alphanumeric characters (including hyphens) in length.
  Note:
  Two clusters are created. Two nodes are created in each cluster. Add details how to identify each cluster/node.
2. For VCN Settings, complete the following fields:
  1. Create New Network: Select this check box if you wish to create a new network resource.
    - If you select this check box, the Create New Network wizard appears allowing you to add and edit the new network information.
    - If you do not select this check box, the Create New Network wizard does not appear and the compute node is created with the existing network options in the VCN.
  2. VCN Network Compartment: Compartment in which to create new or to use existing network resources.
  3. New VCN DNS Name: DNS Name to assign to new VCN.
  4. New VCN CIDR: A default CIDR is generated, but you can change it, if needed.
  5. Client Subnet Compartment: Compartment in which to create new or to use existing client subnet.
  6. Client Subnet DNS Name (optional): Name assigned to the client subnet. You can leave this field blank if you want to create a subnet with DNS disabled.
  7. Client Subnet CIDR: A default CIDR is generated, but you can change it, if needed.
  8. Cluster Subnet Compartment: Compartment in which to create or to use existing cluster subnet.
  9. Cluster Subnet DNS Name (optional): Name assigned to cluster subnet. You can leave this field blank if you want to create a subnet with DNS disabled.
  10. Cluster Subnet CIDR: A default CIDR is generated, but you can change it, if needed.
3. For Client Subnet Settings, complete the following fields:
  1. Select Private Subnet to create or use the VCN's private subnet.
    
    Note:
    If you are using a private IP address to access the compute node, you have to set up an IPSec VPN or FastConnect connection. Refer to OCI documentation for more details.
  2. If Private Subnet is not selected, then Assign Public IP is selected by default, and the VCN's public subnet will be used.
  3. Select the Client Subnet Compartment.
  4. Select the Client Subnet from the dropdown.
4. Select the Cluster Subnet Setting from the dropdown. This private subnet is used only for internal cluster communication, and must be different from the Client subnet selection.
5. For Instance Settings, complete the following fields:
  1. Select the primary cluster's availability domain from the Primary Availability Domain dropdown.
  2. Select the standby cluster's availability domain from the Standby Availability Domain dropdown.
  3. Select a Compute Shape. Supported shapes are:
    - VM.Standard2.1
    - VM.Standard2.4
    - VM.Standard2.8
    - VM.Standard2.16
    - VM.Standard2.24
    - VM.Standard3.Flex
    - VM.Standard.E4.Flex
    - VM.Standard.E5.Flex
    Note:
    If you select a Flex shape, then you must enter the Number of OCPUs, and Amount of Memory (GB).
  4. For Custom Volume Sizes- Select this option to customize the size of the new block storage volumes that are built for the compute node.
    Block Storage (Custom Volume Sizes) -
    1. Swap Volume Size: Default value is 256GB
    2. Deployment Volume Size: Default value is 1024GB (includes Trail files, CacheManager, and Config files)
    3. Deployment Volume VPUs: Default value is 20 VPUs
6. For Create Oracle GoldenGate Deployment, complete the following fields:
  1. Deployment Name: Name to assign to the Oracle GoldenGate Deployment.
    Note:
    Deployment name must:
    
    Be no greater than 32 characters in length
    
    Start with a lower or uppercase character
    
    Contain only alphanumeric characters and underscores
  2. Deployment - Autonomous Database: Select if deployment connects to an Autonomous Database. If selected, select the Compartment in which the Autonomous Database resides, and then select the Autonomous Database instance to which the deployment will connect.
7. For Shell Access, paste the SSH Public Key to allow access as the opc user.
8. Click Next.
On the Review page, review the information you provided, select Run apply on the created stack, and then click Create.

You're brought to the Stacks Job Details page. The stack takes a few minutes to create. You can monitor the creation of the compute nodes in the Log section of the page. As the primary and standby clusters and their nodes are created, the following information is outputted to the log for each cluster:

cluster_name
domain
- dns
- ip_address
- ip_type
nodes
- node1 hostname
- node1 ip_address
- node1 ip_type
- node2 hostname
- node2 ip_address
- node2 ip_type

After the status changes to SUCCEEDED, you can view the compute nodes created under Instances.

To review all the resources created as a result of this job, see Review stack resources.

At this stage, the Marketplace Stack deployment includes only network resources, the compute instances and storage (four Virtual Machines (VMs) two for the primary cluster and two for the standby cluster), and allocation of block volume. Next, a startup script runs and installs the Grid Infrastructure (GI) and Oracle GoldenGate. SSH to the primary cluster's node1 as the opc user to monitor /tmp/startupScript.log and know when the deployment is online. See Monitor installation and startup for more information.