Oracle GoldenGate Licensing for
Non-Oracle Databases & Big Data

1. Understanding GoldenGate’s Heterogeneous Architecture

Oracle GoldenGate is not limited to Oracle-to-Oracle replication. Enterprises routinely use it to capture change data from Oracle databases and deliver it to SQL Server, MySQL, PostgreSQL, MongoDB, Kafka, Hadoop, and dozens of other platforms. It also supports replication between two non-Oracle databases without any Oracle database involvement whatsoever.

This heterogeneous capability is precisely what makes GoldenGate valuable — and precisely what makes its licensing complex. Oracle sells different GoldenGate products for different target environments, and each product is independently licensed and independently priced. Owning one module does not entitle you to use another. A standard Oracle GoldenGate licence covers only Oracle-to-Oracle replication; any non-Oracle endpoint requires an additional, separate licence.

The licensing model follows a simple principle: every server where GoldenGate capture or apply processes run must be covered by the correct module licence. In practice, this means heterogeneous replication pipelines are more expensive than Oracle-to-Oracle ones, because you are licensing both sides with different products. Understanding this architecture is the first step to accurate compliance planning.

From a compliance perspective, the heterogeneous model creates a particularly treacherous landscape. When an Oracle LMS or GLAS audit team reviews your GoldenGate installation, they will examine the configuration files in detail. These files explicitly document every source endpoint, every target endpoint, and every adapter in use. If your configuration shows a Kafka adapter but you only own the base Oracle GoldenGate licence, that is an immediate compliance finding. Similarly, if your trail files show data delivery to a SQL Server instance but you lack the Non-Oracle Database module, Oracle will calculate the shortfall at list price plus retrospective support — often stretching back years.

Enterprises with complex data architectures frequently run GoldenGate across five or more platforms simultaneously. A single global deployment might involve Oracle-to-Oracle replication for primary databases, Oracle-to-SQL-Server feeds for regional reporting, Oracle-to-Kafka streaming for real-time analytics, and occasionally even mainframe-to-Oracle migrations for legacy modernisation. Each of these data flows has distinct licensing requirements, and getting any one of them wrong can generate a six-figure audit finding.

“The single most common compliance gap we encounter in GoldenGate audits is a missing Non-Oracle Database module licence. Organisations buy the base product and assume it covers everything — it does not.”

2. GoldenGate Module Licensing: Editions & What Each Covers

Oracle’s GoldenGate product family consists of four distinct licensing modules. Each addresses a different category of source or target system, and each is sold as a separate SKU with its own support stream.

Key principle — licences are additive, not interchangeable. An Oracle-to-SQL Server pipeline requires two separate licences: the base GoldenGate licence for the Oracle side, and the Non-Oracle Database licence for the SQL Server side. If that same pipeline then also streams to Kafka, you need a third licence: GoldenGate for Big Data for the Kafka target. There is no “universal” GoldenGate licence that covers all environments.

3. Licensing Scenarios by Database Platform

The most practical way to understand GoldenGate’s heterogeneous licensing is through concrete scenarios. Below are the most common replication configurations and the specific licences required for each.

Notice that when no Oracle database is involved (e.g., MySQL to PostgreSQL), the base Oracle GoldenGate licence is not required. You purchase the Non-Oracle Database module for both sides. This is a common source of confusion — some teams mistakenly buy the base licence thinking it is always required.

4. GoldenGate for Big Data: Kafka, Hadoop & Streaming Targets

The GoldenGate for Big Data module is designed for streaming change data into big data platforms and messaging systems. It supports Apache Kafka, Hadoop HDFS, HBase, Apache Cassandra, MongoDB, Amazon Kinesis, Elasticsearch, and JMS-compliant message queues, among others.

Its licensing model has one significant advantage over the standard editions: you only licence the source side. The big data target cluster does not require a GoldenGate licence. This is because Oracle recognises that big data clusters can span hundreds of nodes, and licensing each node would be prohibitively expensive and commercially unworkable.

How Big Data Licensing Works in Practice

You count the processors on the server running the GoldenGate capture processes (the source database server). Apply Oracle’s standard per-processor metric with the appropriate core factor (0.5 for Intel/AMD x86). The Kafka brokers, HDFS DataNodes, or Cassandra ring members receiving the data are not licensed.

Multiple adapters, one licence: The Big Data module licence covers all of GoldenGate’s big data adapters on a given server. If you stream from one Oracle database to both Kafka and Hadoop HDFS simultaneously, a single set of Big Data licences (covering the source server) is sufficient. You do not need separate licences for each target technology.

Combining with other modules: If your pipeline runs Oracle → Kafka, you need both the base GoldenGate licence (for the Oracle capture side) and the Big Data module licence (for the Kafka delivery). If the source is SQL Server → Kafka, you need the Non-Oracle Database module (for the SQL Server capture) plus the Big Data module. The Big Data module never replaces the source-side licence — it supplements it.

5. GoldenGate for Mainframe: DB2 z/OS, VSAM & IMS

The GoldenGate for Mainframe module enables change data capture from mainframe data stores including IBM DB2 on z/OS, VSAM files, IMS databases, and Adabas. At approximately $100,000 per processor (list price), it is by far the most expensive GoldenGate module — roughly five to six times the cost of the base or Non-Oracle editions.

This pricing reflects the niche, complex nature of mainframe integration. Mainframe environments define “processors” differently (using MIPS, MSUs, or engine counts), and Oracle’s mainframe-specific pricing acknowledges the high value of extracting data from legacy platforms that are often decades old and deeply embedded in business-critical processes.

In our advisory practice, we find that many organisations explore GoldenGate for Mainframe during legacy modernisation initiatives — migrating data from DB2 z/OS into cloud-native databases or data lakes. The licensing cost is often the factor that determines whether GoldenGate or an alternative CDC tool is selected. Always model the full licence and support cost before committing to an architecture decision.

6. Per-Processor Pricing & Cost Modelling

All GoldenGate modules follow Oracle’s standard per-processor licensing metric. On-premises, you count physical cores on each server where GoldenGate runs and multiply by the applicable core factor (0.5 for Intel/AMD x86 processors). In the cloud, the core factor does not apply — you use the 2:1 vCPU-to-licence ratio instead.

Negotiated pricing: Few enterprises pay full list price. Discounts of 30–50% are common for GoldenGate when bundled with other Oracle products (database, cloud credits, middleware). For the Mainframe module, discounts can reach 50–60% in large enterprise agreements. Always negotiate — and time your purchase around Oracle’s fiscal quarter-end for maximum leverage.

Cloud pricing works differently. In AWS and Azure, you deploy GoldenGate under a BYOL (Bring Your Own Licence) model. Oracle counts 2 vCPUs as 1 processor licence — the on-premises core factor table does not apply. An 8-vCPU EC2 instance requires 4 processor licences. On OCI, you can use either BYOL or the GoldenGate managed service, which is billed per OCPU per hour (approximately $0.32/OCPU-hour). For steady-state replication workloads, on-premises perpetual licences often have a lower total cost of ownership over five years than cloud metered pricing. For bursty or temporary workloads, cloud pay-as-you-go can be significantly cheaper. Model both options before committing.

For a complete breakdown of Oracle’s pricing methodology, including how to read the price list and calculate processor counts, see Oracle Technology Price List — How to Calculate Pricing.

7. Compliance Risks in Heterogeneous Environments

Heterogeneous GoldenGate deployments carry significantly higher compliance risk than Oracle-to-Oracle configurations. The multi-module licensing model creates multiple points where organisations can inadvertently deploy the wrong licence or forget to licence a newly added endpoint.

Oracle’s LMS and GLAS audit teams are well-versed in identifying GoldenGate module mismatches. During an audit, they will request your GoldenGate configuration files, which explicitly show source and target endpoints, adapters in use, and process types. There is no ambiguity — if you are streaming to Kafka, the configuration files will show Kafka adapters, and Oracle will expect Big Data module licences.

“GoldenGate configuration files are the audit equivalent of a confession. Every source, target, and adapter is documented in plain text. There is no way to obscure what you are replicating to or from.”

8. Licensing Non-Production, DR & Test Environments

A persistent misconception is that non-production environments (development, testing, QA, staging, disaster recovery) do not require GoldenGate licences. This is incorrect. Oracle requires licensing for any environment where GoldenGate software is installed and/or running, regardless of whether it is production or not.

There is no discounted or free GoldenGate licence for non-production use. If you install GoldenGate on a test server to validate a data migration, that server must be licensed with the appropriate module at the same per-processor cost as your production servers. The only exception is GoldenGate Free, a containerised edition suitable for development and proof-of-concept work, but it has functional limitations and is not intended for production workloads.

Strategies to Minimise Non-Production Licensing Costs

9. Negotiation & Optimisation Strategies

GoldenGate’s multi-module licensing model creates both risk and opportunity. The risk is overspending on redundant or incorrectly scoped licences. The opportunity is leveraging the complexity to negotiate better terms with Oracle.

ULA consideration: If your organisation anticipates deploying GoldenGate across dozens of systems and multiple modules, explore an Unlimited License Agreement (ULA) that includes GoldenGate. A well-structured ULA provides cost certainty and unlimited deployment rights for a fixed period (typically three years). However, ULAs require rigorous tracking and governance — at certification time, you must accurately count every deployment. Only pursue a GoldenGate ULA if you have the operational maturity to manage it.

For detailed negotiation tactics, see our dedicated guide: GoldenGate Licensing Negotiation Strategies for CIOs and CTOs.

10. Action Plan: Getting Your GoldenGate Licensing Right

Bringing your GoldenGate licensing into full compliance across heterogeneous environments requires a structured approach. Below is a step-by-step action plan suitable for CIOs, IT procurement leaders, and software asset managers.