Upgrade Oracle GoldenGate Maximum Availability Hub Stack

Learn to upgrade an existing Oracle GoldenGate Marketplace stack using OCI Stacks.

Note: You can only upgrade to Single region - Primary or Standby configuration.

Before you upgrade, ensure that you:

• Shut down all Oracle GoldenGate processes in the VM instance.

• Back up all block storage, in case you need to revert back in the future because of a failed upgrade or update.

• Take note of or backup any files and configuration settings saved on the VMs that are located outside of the GoldenGate block volume so you can reapply them after the stack upgrade.

• Have the most recent GoldenGate deployment password to use for the upgrade, whether manually entered or stored in your Vault secret.

About Stacks

Stacks are zip files that contain the latest Terraform code base. Stacks enable you to provision a new compute node and attach your existing block storage. This approach ensures that Oracle GoldenGate does not lose any associated data present in the environment.

Download the latest stack

Before you upgrade Oracle GoldenGate Marketplace, you have to download the latest stack. To download the stack:

1. Log in to Oracle Cloud Infrastructure.

2. In the Oracle Cloud navigation menu, select Marketplace, and then All applications.

3. Enter Oracle GoldenGate Maximum Availability Hub into the Marketplace search bar.

4. On the Oracle GoldenGate Maximum Availability Hub page, select the Download link located beneath the Launch Stack button.

Identify the stack’s Terraform version

Before you upgrade the stack, identify the Terraform version of the stack to upgrade.

To identify the stack’s Terraform version:

1. Log in to Oracle Cloud Infrastructure.

2. In the Oracle Cloud navigation menu, select Developer Services, and then under Resource Manager, select Stacks.

3. On the Stacks page, select the stack that you want to upgrade.

4. On the Stack details page, under Stack Information, locate the Terraform version field and take note of its value.

Upgrade an Oracle Oracle GoldenGate Maximum Availability Hub image

To upgrade an existing Oracle GoldenGate Maximum Availability Hub image:

1. Download the latest stack.

2. In the Oracle Cloud navigation menu, select Developer Services, and then under Resource Manager, select Stacks.

3. On the Stacks page, select the stack to upgrade.

4. On the Stack’s details page, select Edit, then select Edit stack.

5. On the Edit stack page, for Terraform configuration source, select Browse, and upload the latest stack zip file.

6. Select Next.

7. Review the OGG Password and Cluster’s Instance settings on the Configure variables page, and then select Next.

   Note:

   • For GoldenGate deployment password, ensure that you use the most recent password (either manually entered or stored in your Vault secret).

   • You can only upgrade to Single region - Primary or Standby cluster configuration.

8. Review your stack settings, and then select Save changes.

9. Log in to your Oracle GoldenGate instance and stop all running processes. Ensure that you stop all Microservices (Administration, Distribution, Receiver, and Performance Metrics), including Service Manager.

10. Back in Oracle Cloud, from the navigation menu, select Compute, and then select Instances.

11. On the Instances page, select the instance to upgrade, and then select Terminate.

    Note:

    You can:

    • Select the instance and then select Terminate on the Instance details page

    • Check the box next to the instance in the list, and then select Terminate from the Actions menu

    • Open the instance's Actions (three dots) menu and then select Terminate.

12. In the Terminate instance dialog, select Permanently delete attached boot volume, and then select Terminate instance.

13. After the instance is terminated, use the Oracle Cloud navigation menu to return to the Stacks page.

14. On the Stacks page, select the stack to upgrade. It must be the same one you edited earlier.

15. On the Stack’s details page, select Apply.

After the job completes, verify that the compute node is running. Monitor the /tmp/startupScript.log on the primary cluster’s node-1 to check if the deployment startup succeeded. You can then access the deployment.