Oracle Details Azure Portal Setup for GoldenGate Replication

Oracle’s new walkthrough lays out an Azure-native path for provisioning replication resources, though some deployment choices and administrative access still depend on OCI and private networking.

By 2 min read
Oracle Details Azure Portal Setup for GoldenGate Replication
Oracle Details Azure Portal Setup for GoldenGate Replication

Listen to this story

The audio brief

About 1:40
0:001:40
Read transcript
Oracle has published a step-by-step Azure Portal workflow for setting up GoldenGate, its managed service for real-time data movement. The interface now lets administrators create a GoldenGate deployment, add source or target connections, and link them for replication—while the underlying resources are still mapped into Oracle Cloud Infrastructure. Azure Portal support for these tasks arrived on August 28, and Oracle’s September 22 guide spells out how the current experience works. The process starts with a deployment: the managed environment where GoldenGate replication runs. Teams can create Oracle Database or BigData deployments, sized from one to 24 OCPUs, with optional autoscaling. They can then add connections for Oracle Database, Kafka, or Microsoft Fabric, and assign those connections from either the deployment page or the connection page. The Azure workflow is simpler, but it is not complete feature parity with OCI Console. Some deployment and connection types still require Oracle’s OCI interface. Provisioning can also take an hour or more, and a deployment must be active before connections can be assigned. Networking is the important operational detail. A Resource Anchor maps the Azure request to an OCI compartment. A Network Anchor maps it to an Azure virtual network and subnet, and is required for a dedicated private endpoint. There is no default internet-facing endpoint, so administrators need a network path into the deployment. The key constraint is whether that Azure-native setup provides enough coverage and connectivity for a team’s specific GoldenGate topology.

Story brief

3 key points

Oracle has expanded its Azure-native control plane for GoldenGate, with a September 22 guide documenting deployment and connection management through Azure Portal while resources remain mapped to Oracle Cloud Infrastructure. The workflow supports Oracle Database and BigData deployments sized from one to 24 OCPUs, optional autoscaling, and shared or private endpoints. It simplifies initial provisioning but is not...

  1. 01

    Azure Portal support for GoldenGate deployment and connection management was added August 28; Oracle’s September 22 guide documents the workflow.

  2. 02

    Supported connection types are Oracle Database, Kafka, and Microsoft Fabric; additional deployment and connection types remain OCI Console-only.

  3. 03

    Deployments support one to 24 OCPUs, optional autoscaling, and shared-endpoint or dedicated private-endpoint routing.

Oracle has published a detailed Azure Portal workflow for setting up GoldenGate, its managed service for real-time data movement. Customers can create a GoldenGate runtime, add source or target connections, and link them for replication from the Azure interface—while still mapping those resources into Oracle Cloud Infrastructure.

The September 22 walkthrough is a practical guide to the native interface for Oracle GoldenGate on Oracle AI Database@Azure. Oracle’s change log says Azure Portal support for creating and managing GoldenGate deployments and connections was added on August 28; the new material specifies the steps and current boundaries of that experience.

Administrators first create a deployment, the managed environment where GoldenGate replication processes run. They then create a connection for a source or target system and assign it to that deployment. The portal currently supports connections for Oracle Database, Kafka and Microsoft Fabric.

What the Azure workflow currently includes

  • Create OracleDatabase or BigData deployments, with one to 24 OCPUs and optional autoscaling.
  • Choose shared-endpoint routing or a dedicated private endpoint for a connection.
  • Assign a connection from the deployment page, or assign a deployment from the connection page.

The setup relies on two mapping objects. A Resource Anchor identifies the OCI compartment where the Oracle resource is created, while a Network Anchor identifies the Azure virtual network and subnet used by a deployment. That lets teams use Azure subscriptions, resource groups, regions and tags in provisioning, but it does not remove the underlying Azure-to-OCI relationship.

Oracle says deployment creation can take an hour or more, and a deployment must be active before connections are assigned. Dedicated endpoint routing requires a Network Anchor. The GoldenGate console is not exposed through an internet-facing public endpoint by default in this portal flow, so administrators also need a network path capable of reaching the deployment.

Sources

  1. docs.oracle.comdocs.oracle.com
  2. blogs.oracle.comNative UI for Oracle GoldenGate on Oracle AI Database@Azure

Loading discussion...

YOUR READING SPACE

Notifications