Known issues

Discover some common issues you may encounter while using Oracle GoldenGate Maximum Availability Hub and how to work around them.

Terraform destroy fails if instances are in stopped state

Description: If nodes created by the Oracle GoldenGate Maximum Availability Hub stack are in a Stopped state, terraform destroy fails.

Workaround: You can perform a terraform destroy on the stack even when instances are stopped.

Normal Oracle GoldenGate 19 and 21 listings don't attach secondary VNIC, while Oracle GoldenGate Maximum Availability Hub requires a secondary VNIC. When trying to destroy the stack, it would attempt to detach the secondary VNIC and in order to do that, the instance should be running. If the instance is down, then it fails to detach the secondary VNIC.

If there are failures for the resource in the terraform destroy logs, you can destroy the resources in the Oracle Cloud console. Once you destroy the resources that were failing, then run the destroy stack again then it should proceed without error. Note that when you destroy the instance, it also destroys all associated resources.