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 network settings, and starts the Grid Infrastructure and Oracle GoldenGate installations.

Before you begin

Ensure that you add all required policies before you proceed.
If configuring cross region or hybrid clusters:
- Take note the regions in which the primary and standby clusters will reside. You'll need to to switch regions while making configuration settings. Ensure that you have the proper access permissions to these regions.
- Ensure that you set up remote VCN peering.
For single region clusters, 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 lowercase characters (including hyphens) in length.
  3. 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
  Note:
  Two clusters are created. Two nodes are created in each cluster. Add details how to identify each cluster/node.
2. For Specify OGG Password, choose to either set the OGG password manually, or use a password secret. Learn more about Vault and secrets.
3. For Cluster configuration(s), select one of the following:
  - Multi Region - Primary and Standby Clusters: Create Primary and Standby Clusters in different regions.
    
    Note:
    Ensure that you have the proper access permissions to these regions.
  - Single Region - Primary and Standby Clusters: Create Primary and Standby Clusters within the same region.
  - Single Region - Primary Cluster only: Create only a Primary Cluster in the selected region.
  - Single Region - Standby Cluster only: Create only a Standby Cluster in the selected region.
4. For Availability Domain, select an Availability Domain (AD) in the selected region.
  
  Note:
  If configuring Multi Region Primary and Standby Clusters, you'll first configure the Primary cluster in the selected region, and then change regions when prompted using the Region Selector to configure the Standby cluster.
5. 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.
6. 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.
7. For Cluster Subnet Setting, from the dropdown.
  1. Select a Cluster Subnet Compartment from the dropdown.
  2. Select a Cluster Subnet from the dropdown. This private subnet is used only for internal cluster communication, and must be different from the Client subnet selection.
8. For Autonomous Database Settings, select Fetch Wallet Details, only if using Autonomous Database (ADB), then select the Compartment where your ADB resides and then your ADB instance.
9. (Multi Region - Primary and Standby only) Select Standby Cluster Settings, to start configuring the Standby cluster.
  1. Using the Region selector in the Oracle Cloud global navigation bar, select the region in which to create the Standby cluster. This region must be different than that of the Primary cluster.
  2. Repeat steps 7d to 7h to configure the Standby cluster.
10. (Multi Region - Primary and Standby only) For Stack Management, select Manage Stack in Primary Cluster to manage the stack only from the Primary cluster region. If not selected, the stack can also be managed from the Standby cluster region.
11. For Cluster Instance Settings, complete the following fields:
  For Standby only configurations:
  1. Mount point of the primary cluster
  2. Oracle UID, must be the same UID of the primary cluster oracle user.
  3. Grid UID, must be the same UID of the primary cluster grid user.
  4. GID for oinstall, must be the same GID of the primary cluster oracle user.
  For all configurations:
  1. Select a Compute Shape. Supported shapes are:
    - 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).
  2. 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. Minimum of 128GB.
    2. Deployment Volume Size: Default value is 1024GB (includes Trail files, CacheManager, and Config files). Minimum of 512GB.
    3. Deployment Volume VPUs: Default value is 20 VPUs. Minimum of 10VPUs.
      
      Note:
      For Single Region - Standby Cluster only, this value must be greater than or equal to that of the Primary Cluster.
  3. Paste the SSH Public Key to allow access as the opc user.
12. 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 in single- and multi-region cluster configurations, or two VMs is primary cluster or standby cluster only configurations), 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 for single-, multi- region, or primary only cluster configurations, or standby cluster's node1 for standby cluster only configuration, as the opc user to monitor /tmp/startupScript.log and know when the deployment is online. See Monitor installation and startup for more information.