Use OCI GoldenGate on Google Cloud
Prepare the Google Cloud network and permissions, then provision GoldenGate deployments, connections, and assignments from Google Cloud Console, the Google Cloud CLI, or the API. Use the shared OCI GoldenGate documentation for connection compatibility and runtime configuration.
Where you work: Create and manage Google Cloud GoldenGate resources in Google Cloud. Use the OCI GoldenGate documentation for supported source and target combinations and for Extract, Distribution Path, Replicat, and Data Transforms configuration.
Before you begin
- A Google Cloud project with billing enabled and the Oracle AI Database@Google Cloud API enabled.
- An IPv4 VPC in the same Google Cloud project as the Oracle AI Database@Google Cloud resources.
- Google Cloud IAM roles for VPC networking, ODB Network and ODB Subnets, GoldenGate deployments, GoldenGate connections, and GoldenGate connection assignments.
- OCI policies for GoldenGate, virtual-network resources, Vault, Keys, and Secrets, plus a GoldenGate deployment dynamic group that can read secret bundles.
Prepare the Google Cloud network
-
Use an IPv4 VPC in the Google Cloud project that hosts Oracle AI Database@Google Cloud resources.
-
Create it in the Marketplace-order project and in the same region and zone planned for GoldenGate. It connects Oracle AI Database@Google Cloud resources to the Google Cloud VPC.
-
Use a non-overlapping CIDR range and the
client_subnetpurpose. GoldenGate deployments and Autonomous AI Database require a Client ODB Subnet. -
Confirm connectivity.
Plan HTTPS access to the GoldenGate console (443), Oracle database connectivity (typically 1521 or 1522), and required Big Data target access (443). Configure DNS and routing for every intended source and target.
Provision and validate GoldenGate resources
-
In Google Cloud, select the same region, Google Cloud Oracle zone, and Client ODB Subnet as the ODB Network. Select the deployment technology, license model, environment type, OCPU count, auto-scaling setting, and administrator credentials.
-
Create the source and target connections.
Select supported connection types from the shared OCI GoldenGate support matrix. Choose shared or dedicated routing: a shared endpoint uses the assigned deployment’s ingress IPs; a dedicated endpoint has its own private endpoint and ingress IPs.
-
Assign each connection to the required deployment and test every assignment before creating Extract, Distribution Path, Replicat, or Data Transforms components.
-
Verify the foundation.
In Google Cloud or OCI Console, go to your GoldenGate deployment and verify the deployment and connection assignments are available.
Google Cloud private connectivity guidance
- For Autonomous AI Transaction Processing and Autonomous AI Lakehouse, OCI GoldenGate creates private endpoints over port 1522 unless secure access from everywhere is selected.
- When you select the Autonomous AI Database while creating the connection, the private endpoint is created automatically. Otherwise, configure shared-endpoint security rules and DNS in the selected subnet.
- Create a GoldenGate-to-GoldenGate connection only when the topology needs one deployment to connect to another, such as a Distribution Path between an Oracle and a Big Data deployment.