Known issues related to GoldenGate @ Oracle AI Database@Azure
Resource anchor pending or fails
Confirm that your Azure account has Contributor role on the target Resource Group and that the Oracle AI Database@Azure resource provider is registered under Azure, Subscriptions, then Resource Providers.
Network anchor fails with subnet delegation error
You must delegate the subnet to Oracle AI Database@Azure before you create the Network Anchor. In the Azure Portal, select Virtual Networks, Subnets, then Delegation and confirm the correct delegation is set.
OCI compartment not visible after Resource Anchor creation
Wait up to five minutes for propagation. If it still does not appear, confirm the Resource Anchor shows Active in the Azure Portal. If it shows Failed, delete and recreate it.
odbaa-goldengate-administrators group doesn’t exist
Your tenancy was likely provisioned before October 7, 2025. Run the Cloud Shell automation script in Step 3 to create the group and policies in one step.
Common issues encountered with deployment creation
If the dynamic group goldengate-deployments is not applied correctly, then you’re likely encounter one or more of the following issues during deployment creation:
-
Azure availability zone value does not match the Network Anchor (zone mismatch — most common)
-
Service quota for Vault, key, Secret or Load Balancer has been reached in the target region
-
The Vault secret or encryption key is in a different compartment without cross-compartment policy
Deployment blocked by authorization error
Confirm the dynamic group goldengate-deployments exists. In the Oracle Cloud navigation menu, select Identity & Security, Dynamic Groups, and then check that its matching rule is correct. Verify policies granting the group access to manage secret-family, vaults, and keys are scoped to the correct compartment.
Deployment stuck in creating state, or failed
On the deployment details page, switch to the Work Requests tab and review messages for errors. Common causes include:
-
Zone mismatch — the logical availability zone does not match the Network Anchor. Recreate the Network Anchor with the correct zone, then recreate the deployment.
-
Load Balancer quota reached — use the OCI search bar to search for Limits, Quotas and Usage, then filter by ORACLEDBATAZURE, and request an increase if needed.
-
Vault secret or key inaccessible — confirm the secret and key are in the same compartment as the deployment, or that cross-compartment policies exist.
Deployment not visible in Azure Portal
A subscription other than ORACLEDBATAZURE was selected during creation. Delete the deployment and recreate it with the correct subscription.
Plain text password rejected
The password must be at least 8 characters and include one uppercase letter, one lowercase letter, one number, and one special character. It must not contain the username.
Vault secret inaccessible
Confirm the secret state is Active. In the Oracle Cloud navigation menu, select Identity & Security, then Secret Management. Secrets that are pending deletion cannot be used.
Connection unable to access database
Confirm the required database port is open in both the Azure NSG and the OCI security list on the Network Anchor-mapped subnet. If using a hostname, verify DNS resolution is configured per the DNS Resolution for Network Anchors documentation linked in Task 1, Step 2.