Understanding Oracle GoldenGate Edition Structure

Oracle GoldenGate is Oracle's real-time data replication and streaming platform. It captures transactional changes at the database level and applies them to target systems with minimal latency, supporting Oracle-to-Oracle replication, Oracle-to-non-Oracle replication, non-Oracle-to-non-Oracle replication, and delivery to big data targets including Hadoop, Apache Kafka, Elasticsearch, and NoSQL stores.

A fundamental and widely misunderstood aspect of GoldenGate licensing is that Oracle sells GoldenGate as a family of distinct products, not as a single licence that covers all replication scenarios. Owning a base GoldenGate licence does not entitle the holder to use non-Oracle database connectors or big data adapters. Each expansion of the GoldenGate footprint to cover new database platforms or big data targets requires a separate, additive licence purchase.

For organisations building heterogeneous data integration architectures — which represents the majority of modern enterprise deployments — this product segmentation creates both significant licence cost exposure and substantial audit risk if the distinctions are not clearly understood.

Oracle GoldenGate Product Lines and Their Scope

Oracle GoldenGate (Base)

The base GoldenGate licence covers replication between Oracle Database instances. It provides Oracle-to-Oracle real-time change data capture, replication across Oracle versions and platforms, and support for Oracle Database high availability configurations. The base licence does not permit any connectivity to non-Oracle database systems as either source or target.

Oracle GoldenGate for Non-Oracle Database

This edition extends GoldenGate capabilities to non-Oracle source and target databases. It enables replication from SQL Server, MySQL, PostgreSQL, Sybase, DB2, Teradata, and other database platforms — either as sources feeding Oracle targets, as Oracle feeding non-Oracle targets, or between non-Oracle systems entirely. A separate GoldenGate for Non-Oracle Database licence is required for each non-Oracle database platform included in a GoldenGate topology.

Oracle GoldenGate for Non-Oracle Database is priced at approximately $17,500 per processor licence, consistent with the base GoldenGate price. Annual support at 22 percent of the net licence price means approximately $3,850 per processor per year in ongoing support costs, increasing by 8 percent each year under Oracle's standard escalation terms.

Oracle GoldenGate for Big Data

Oracle GoldenGate for Big Data enables delivery from Oracle or non-Oracle database sources to big data target systems. It provides adapters for Apache Kafka, Hadoop (HDFS), HBase, Cassandra, Elasticsearch, MongoDB, Amazon S3, Google BigQuery, and various other analytics and streaming platforms. The Big Data edition is specifically designed for event streaming and data lake ingestion use cases.

Oracle GoldenGate for Big Data is priced at approximately $20,000 per processor licence — a higher price point than the base or Non-Oracle Database editions, reflecting Oracle's positioning of big data integration as a premium capability. Annual support at 22 percent is approximately $4,400 per processor per year.

Oracle GoldenGate for Mainframe

The most expensive GoldenGate edition, GoldenGate for Mainframe provides connectivity to IBM mainframe systems (DB2 for z/OS, VSAM). Mainframe edition pricing is approximately $100,000 per processor, reflecting the specialised nature and limited competition in the mainframe integration space. Organisations with mainframe integration requirements should treat GoldenGate for Mainframe licensing as a separate commercial negotiation from the rest of their GoldenGate footprint.

Need an independent GoldenGate licence review?

We identify non-Oracle and big data licensing gaps before Oracle does.
Request Review →

Processor Licensing: Source and Target Requirements

Oracle GoldenGate is licenced on a Processor basis. Unlike Oracle Database, where licensing is confined to the servers running the database, GoldenGate licensing must cover both the source system (where the Extract process captures changes) and the target system (where the Replicat process applies changes). This bidirectional licensing requirement is the most common source of underestimation in GoldenGate licence cost models.

If GoldenGate is extracting from a 16-core source server and applying to a 16-core target server, with Intel processors carrying Oracle's 0.5 core factor, the source requires 8 processor licences and the target requires 8 processor licences — for a total of 16 GoldenGate processor licences. An organisation that models only the source-side requirement will underestimate the licence obligation by 50 percent.

This source-and-target rule applies to both the base GoldenGate licence and the GoldenGate for Non-Oracle Database edition. The GoldenGate for Big Data edition is an exception: Oracle's policy for the Big Data edition requires licensing only on the source database side. The big data target cluster nodes — the Kafka brokers, Hadoop nodes, or Elasticsearch servers — do not require GoldenGate for Big Data licences. This exception makes the Big Data edition cost model more predictable and is an important consideration when comparing licensing costs across different GoldenGate use cases.

Compliance Risks in Heterogeneous GoldenGate Deployments

Oracle LMS audits of GoldenGate deployments frequently identify non-Oracle and big data extension usage without the corresponding licences in place. The three most common compliance failures are: deploying GoldenGate to replicate to or from a non-Oracle database without purchasing GoldenGate for Non-Oracle Database; using GoldenGate for Big Data adapters under a base GoldenGate or Non-Oracle Database licence; and failing to licence GoldenGate on target system processors, particularly in cloud environments where target infrastructure scales independently of the source.

A fourth compliance risk is non-production environments. Oracle's licensing policy applies to all environments where GoldenGate is installed and running — production, disaster recovery, test, and development. Organisations that licence only their production environments and deploy GoldenGate in non-production for testing or disaster recovery readiness without corresponding licences are non-compliant. Oracle's audits typically request a complete inventory of all environments, and the non-production exposure can represent a significant portion of the total audit claim.

Oracle GoldenGate Licensing in Cloud Environments

Cloud deployments add additional complexity to GoldenGate licensing. In Oracle's own cloud (OCI), GoldenGate is available as a managed service (OCI GoldenGate) priced on an OCPU-hour basis. OCI GoldenGate includes the GoldenGate software licence within the service fee, making it an all-inclusive consumption model. Organisations with existing on-premises GoldenGate licences can use Bring Your Own Licence (BYOL) mode on OCI to reduce the OCPU hourly rate.

In AWS and Azure, Oracle counts two vCPUs as one Processor licence for GoldenGate running on virtual machines. An EC2 instance with 32 vCPUs requires 16 GoldenGate processor licences. The same rule applies to the target environments — a 32-vCPU RDS instance used as a GoldenGate replication target requires 16 processor licences for the applicable GoldenGate edition.

Oracle's cloud licensing policies for GoldenGate are governed by the Oracle Cloud Licensing Policy document. Organisations deploying GoldenGate in multi-cloud environments should verify the current policy document before procurement, as cloud licensing rules for Oracle products have been subject to periodic revision.

"Most GoldenGate deployments underestimate licence cost by at least 50 percent because they model only the source side. The target side is equally licensable — and auditors know exactly where to look."

Strategies to Optimise GoldenGate Licensing Costs

Conduct a complete topology inventory. Document every GoldenGate Extract, Pump, and Replicat process in your deployment — including the host system, processor configuration, and database platform for each. Map this inventory against your licence holdings to identify gaps before an Oracle audit does.

Evaluate whether OCI GoldenGate reduces cost. For cloud-native or cloud-migration use cases, OCI GoldenGate's consumption-based model may be more cost-effective than perpetual licences plus 22 percent annual support, particularly for workloads with variable or declining volume. Model the five-year cost comparison including licence, support, and BYOL alternatives.

Challenge processor counts in virtualised environments. Oracle's core factor and vCPU counting rules are well-defined but frequently misapplied by Oracle auditors. Ensure your processor licence calculations use the correct core factor for your specific hardware, and document your virtualisation configurations to withstand audit scrutiny.

Negotiate GoldenGate as part of a broader Oracle deal. GoldenGate is one component in Oracle's data integration portfolio. Including GoldenGate licence requirements in a broader Oracle contract negotiation — alongside Oracle Database, Fusion Middleware, or cloud services — increases deal value and negotiating leverage. Oracle's discount levels for bundled deals consistently exceed those achievable on standalone GoldenGate negotiations.

Evaluate GoldenGate alternatives. The data integration market offers a range of alternatives to Oracle GoldenGate for heterogeneous replication and big data integration use cases. Striim, Debezium (open-source), AWS Database Migration Service, Azure Database Migration, and Fivetran offer heterogeneous CDC and replication capabilities at substantially different price points. An independent cost comparison validates whether GoldenGate's premium pricing is justified for your specific use case.

Oracle Licensing Updates

Subscribe to our Oracle Knowledge Hub for independent analysis of Oracle licensing changes and audit trends.

Key Actions Before Your Next GoldenGate Renewal

Audit every GoldenGate process. Map all Extract, Pump, and Replicat processes to their host environments. Verify that GoldenGate for Non-Oracle Database and Big Data licences cover every non-Oracle and big data target or source in your topology.

Verify target-side licensing. Confirm that every target system running a Replicat process is licensed under the applicable GoldenGate edition. This is the most common audit finding in GoldenGate deployments.

Include non-production environments. Document test, development, and disaster recovery GoldenGate deployments and ensure they are covered by your licence entitlement or that Oracle's non-production provisions, if any, apply.

Benchmark support costs. At the current 22 percent annual support rate, escalating at 8 percent per year, GoldenGate support becomes progressively more expensive. Compare the value of Oracle support against Oracle's current product roadmap for GoldenGate and the cost of OCI GoldenGate as a managed alternative.