Oracle GoldenGate Licensing Guide 2026

1. What Is Oracle GoldenGate?

Oracle GoldenGate is a real-time data integration and replication platform that captures database changes at the transaction log level and delivers them to one or more target systems with sub-second latency. First developed by GoldenGate Software and acquired by Oracle in 2009, it has become the most widely deployed enterprise replication solution for heterogeneous database environments involving Oracle, SQL Server, MySQL, PostgreSQL, IBM Db2, Teradata, and others.

Organisations deploy GoldenGate for four primary purposes: zero-downtime database migrations, active-active high availability, real-time data warehousing and analytics feeds, and disaster recovery with a validated recovery point objective measured in seconds rather than hours. Because it operates at the redo log level rather than through SQL, it imposes minimal overhead on source databases and can capture changes from systems that cannot tolerate significant additional query load.

The licensing complexity stems from three facts. First, GoldenGate is sold in multiple editions with different price points and permitted use cases. Second, Oracle counts processors on both source and target systems, which can double — or more than double — the licence cost relative to what customers anticipate at the outset. Third, the product is frequently deployed across cloud infrastructure where the relationship between physical processors, virtual CPUs, and Oracle's core factor table introduces additional exposure.

This guide covers everything a procurement lead, IT director, or licensing manager needs to understand Oracle GoldenGate licensing in 2026, including the implications of the GoldenGate 26ai release announced in January 2026.

2. GoldenGate Editions Explained

Oracle sells GoldenGate under five main product names, each designed for a specific replication scenario. Understanding which edition applies to your architecture is the starting point for every cost model.

GoldenGate Base Edition

The Base Edition licences replication between Oracle databases only. This is the entry-level product, list-priced at $17,500 per processor. It covers Extract (source capture), Data Pump (optional intermediate routing), and Replicat (target apply) components. The Base Edition is appropriate for Oracle-to-Oracle migrations, Oracle active-active clusters, and real-time Oracle-to-Oracle data warehousing feeds. It cannot be used to replicate to or from non-Oracle databases; attempting to do so without the correct licence is one of the most common audit findings.

GoldenGate for Non-Oracle Databases

This edition licences replication where at least one endpoint — source or target — is a non-Oracle database. Supported databases in this category include SQL Server, MySQL, PostgreSQL, IBM Db2 LUW, Sybase/SAP ASE, Teradata, and others. The list price is $17,500 per processor, the same as the Base Edition, but the processor count must include processors on both the non-Oracle source and the target. Many organisations assume that because the price per processor is identical, there is no material difference — the difference lies in scope and audit exposure when the wrong edition is deployed.

GoldenGate for Big Data

The Big Data edition permits replication to Apache Kafka, Apache Hadoop (HDFS), Apache Hive, Oracle NoSQL, Cassandra, MongoDB, and other big-data targets. It is list-priced at $20,000 per processor. The higher price point reflects the fact that big-data targets typically involve many more nodes, each of which can carry processor licence obligations. Organisations building real-time analytics pipelines from Oracle or non-Oracle transactional sources into Kafka or Hadoop estates frequently encounter significant unexpected costs when the processor rule is correctly applied across all Kafka broker and Hadoop worker nodes.

GoldenGate for Mainframe

Mainframe replication — covering IBM z/OS and IBM iSeries (AS/400) sources or targets — is licensed at $100,000 per processor. Given the complexity of IBM mainframe core counting, which uses MIPS-based calculations rather than Oracle's standard processor metric, organisations deploying GoldenGate in mainframe environments should obtain independent licensing advice before signing contracts. A single under-counted mainframe CPU can represent a material compliance gap.

GoldenGate Veridata

Veridata is a companion product that compares data between source and target systems to confirm that replication has not introduced errors or drift. It is sold separately at $10,000 per processor and is licensed on the same processor metric as the base product. Veridata is often overlooked in initial procurement discussions but becomes relevant when organisations need to demonstrate data integrity for regulatory compliance or when validating a migration before cutover.

Which Edition Do You Need?

The rule is simple but strictly enforced by Oracle's Licence Management Services (LMS) team: you need the highest-tier edition applicable to any endpoint in your replication topology. If you replicate Oracle-to-Oracle in production but also have a development environment replicating Oracle-to-MySQL, the Non-Oracle Database edition applies to your entire environment. Mixing editions to minimise cost across environments without clear contractual separation is a common audit risk factor.

3. Processor Metric and Core Factor Table

GoldenGate is licensed on the Processor metric, not Named User Plus. One Processor licence is required for each processor on which the GoldenGate software is installed and running, adjusted by Oracle's Core Factor Table.

The Core Factor Table assigns a multiplier to each processor architecture, reflecting Oracle's view of relative compute power. For the most common server architectures in 2026:

For virtualised environments, Oracle's policy is that all physical cores in the host (or cluster, for vSphere clusters with vMotion enabled) must be counted unless hard partitioning is in place. Oracle-approved hard partitioning options include Oracle VM, IBM LPAR (with CPU pinning), and Solaris Zones. VMware, Hyper-V, and KVM are not accepted as hard partitioning — a common point of dispute in audits. In those environments, the entire physical host's core count applies.

4. The Source-and-Target Counting Rule

The most important — and most frequently misunderstood — aspect of GoldenGate licensing is the requirement to count processors on both source and target systems. Oracle's product use rights documentation states that licences are required for the processors on which the GoldenGate Extract component runs (the source) and the processors on which the Replicat component runs (the target).

Why This Doubles Your Cost

Consider a standard data warehousing deployment: a production Oracle OLTP database on a 16-core Intel server feeding a 32-core target data warehouse server. The GoldenGate licence calculation is: (16 × 0.5) + (32 × 0.5) = 8 + 16 = 24 processor licences. At $17,500 per licence (Base Edition), that is $420,000 in licence fees, plus 22% annual support of $92,400 — before the 8 percent annual support increase. Many organisations budget based on the source server alone (8 licences, $140,000) and face a significant true-up at audit or renewal.

Multi-Hop and Cascade Topologies

GoldenGate supports multi-hop replication where data passes through one or more intermediate systems before reaching its final target. In cascade topologies, each intermediate hub server on which a Replicat component runs must also be licenced. A three-hop topology (source → hub → target) requires processors to be counted at all three tiers. Organisations implementing hub-and-spoke designs for multi-region replication should model licence costs across every node in the topology before signing.

The Data Pump Exception

Oracle's Data Pump component (the intermediate routing pump within GoldenGate, not to be confused with Oracle Data Pump export/import) runs on the source system and does not add a separate processor licence obligation — it is covered by the Extract-side licence. However, if the Data Pump is moved to a dedicated relay server, that server's processors must be counted.

5. 2026 Pricing Reference Table

The following prices are Oracle's standard list prices as of 2026. Actual transaction prices depend on negotiated discounts, which for GoldenGate typically range from 30% to 60% off list in competitive situations.

The five-year total per processor includes the initial licence fee and four years of support payments, with each year's support increasing by 8 percent from the prior year. An organisation licencing 20 processors of GoldenGate Base Edition faces a five-year total cost of approximately $470,000 — a figure that often surprises buyers who modelled only the initial licence fee at list price.

6. Annual Support: 22% Base, 8% Annual Increases

Oracle charges 22% of the current licence list price per year for Oracle Software Technical Support (Annual Technical Support). For a GoldenGate Base Edition deployment with 20 processor licences at $17,500 list, the year-one support cost is $17,500 × 20 × 22% = $77,000 per year.

The 8 Percent Annual Escalator

Oracle's standard support contract includes an annual support price increase of 8 percent per year. This is not a negotiated rate — it is Oracle's standard contractual position absent a specific cap negotiation. Over a five-year horizon, an initial support payment of $77,000 compounds as follows:

• Year 1: $77,000
• Year 2: $83,160
• Year 3: $89,813
• Year 4: $97,000
• Year 5: $104,756

The cumulative five-year support cost for this example exceeds $451,000 — nearly six times the year-one payment. Organisations that set budget allocations based on year-one support costs without modelling the 8 percent annual escalation routinely find themselves with unsustainable support obligations at contract renewal time.

Negotiating Support Caps

It is possible — though not Oracle's default position — to negotiate a cap on annual support price increases. Oracle has agreed to caps of 0–3% annually for customers who negotiate at the right moment in Oracle's fiscal calendar, which runs to May 31. The Q4 window (March to May) provides maximum leverage as Oracle sales teams face end-of-quarter and end-of-year targets. Customers renewing outside this window have materially less negotiating power.

7. Cloud Licensing: OCI, AWS, Azure

GoldenGate is available in multiple cloud deployment models, each with distinct licensing implications. The choice of cloud platform and pricing model has a direct and often dramatic impact on total cost of ownership.

Oracle Cloud Infrastructure (OCI) — BYOL vs Licence-Included

On OCI, GoldenGate can be deployed under two models. Licence-Included embeds the licence cost in the hourly compute rate — no separate Oracle licence purchase is required. Bring Your Own Licence (BYOL) applies existing on-premises GoldenGate licences to OCI compute, with a 75% discount on the Licence-Included compute rate. For organisations with existing perpetual GoldenGate licences, BYOL on OCI typically produces a 40–60% reduction in total cloud spend versus Licence-Included pricing.

OCI also offers GoldenGate as a fully managed SaaS offering (GoldenGate on OCI), where the service is billed by OCPU-hour and includes the GoldenGate licence, management, patching, and high-availability infrastructure. This model removes the complexity of processor counting and is worth evaluating for net-new deployments where on-premises perpetual licensing is not required.

AWS and Azure — BYOL Only

On Amazon Web Services and Microsoft Azure, GoldenGate is available only under a BYOL model — there is no Oracle-provided Licence-Included option on these platforms. This means on-premises GoldenGate licences can be used on AWS and Azure under Oracle's cloud licensing policy, which allows existing perpetual licences to run on authorised cloud providers. However, Oracle's counting rules apply: each vCPU in the cloud VM is treated as a physical core, and the 0.5 core factor applies for Intel/AMD instances, meaning a 16-vCPU AWS EC2 instance requires 8 Oracle processor licences.

OCI GoldenGate Service vs Self-Managed

For organisations evaluating cloud-native GoldenGate, the managed OCI GoldenGate service eliminates the overhead of infrastructure management, patching, and HA configuration. Pricing is consumption-based by OCPU-hour, making costs predictable and scalable. The trade-off is reduced configuration flexibility compared to self-managed deployments, which matters for complex topologies involving custom Java user exits or non-standard source adapters.

8. GoldenGate 26ai — New Capabilities (January 2026)

Oracle released GoldenGate 26ai in January 2026, marking the product's first major architectural update in several years. The release introduces capabilities with direct implications for both deployments and licensing.

AI Microservice Architecture

GoldenGate 26ai introduces a native AI microservice that enables automated anomaly detection in replication streams, intelligent lag prediction, and natural-language query of replication status and pipeline health. The AI microservice runs as a containerised component within the GoldenGate Microservices Architecture. From a licensing perspective, the AI microservice runs on the same servers as the Extract and Replicat components — it does not introduce new processor licence obligations as a standalone component, but it does require the GoldenGate Microservices Architecture platform, which is included in all current GoldenGate edition licences.

Schema Evolution Support

One of the most operationally significant features in 26ai is automated schema evolution handling. Prior versions of GoldenGate required manual intervention or custom scripts when source table schemas changed — a common source of replication outages during application deployments. GoldenGate 26ai can detect and automatically propagate compatible DDL changes (column additions, data type widening) without pipeline restarts. This capability reduces operational overhead significantly for environments with frequent schema changes.

Expanded Platform Support

GoldenGate 26ai expands the Microservices Architecture to support a broader set of source databases previously available only through the Classic Architecture, including extended PostgreSQL version support and improved MySQL 8.x binlog handling. Organisations running heterogeneous environments with multiple PostgreSQL versions will benefit from the simplified management interface that Microservices Architecture provides.

Licensing Implications of 26ai

GoldenGate 26ai does not change Oracle's edition structure or list pricing. Existing licence holders with current support contracts receive the upgrade as part of their annual support entitlement. The new AI microservice features are included in existing edition licences — Oracle has not introduced a separate "AI add-on" SKU for GoldenGate at this stage. However, customers running GoldenGate under older licence agreements should verify that their contract terms permit deployment of Microservices Architecture components, as some legacy agreements reference "GoldenGate Classic Architecture" specifically.

9. Audit Risk and LMS Compliance

Oracle LMS audits of GoldenGate deployments have increased in frequency since 2022, driven by the growing adoption of cloud-based replication that introduces new counting complexities. The most common compliance gaps identified in audits are consistent across industries and organisation sizes.

Top GoldenGate Audit Findings

• Wrong edition deployed: Using GoldenGate Base Edition when Non-Oracle DB edition is required because of a single non-Oracle endpoint. This is the most common finding and typically the largest financial exposure.
• Target processors not counted: Licencing only the source server processors and ignoring the Replicat-side processor obligation. This routinely results in a true-up of 50–100% of the initially licensed quantity.
• VMware soft partitioning: Running GoldenGate VMs on vSphere clusters and counting only the VMs' vCPUs rather than all physical cores in the cluster eligible for vMotion migration.
• Development and test environments: Deploying GoldenGate in non-production environments without separate licences. Oracle's standard licensing terms do not include a development licence for GoldenGate — each environment requires its own processor licences unless a specific contractual provision exists.
• Cloud overcount: Deploying GoldenGate on AWS or Azure instances with more vCPUs than are covered by the on-premises licence pool, without a formal cloud licence extension.

Preparing for an LMS Audit

If Oracle initiates an audit, the process typically begins with an Audit Notification Letter requesting a software inventory within 30–45 days. Organisations should immediately engage independent licensing counsel before responding. Do not send Oracle any data — inventory scripts, spreadsheets, or configuration files — before reviewing the data with your advisors. Oracle LMS scripts are designed to collect data that can be used to establish breach; they do not collect data that will work in your favour.

Conduct your own internal audit first, using the same methodology Oracle will use: identify all servers where GoldenGate Extract or Replicat components run, count processors using the core factor table, and verify the edition against each endpoint. Document any discrepancies and model the financial exposure before engaging Oracle in a remediation discussion.

10. Five Cost Optimisation Strategies

Organisations with significant GoldenGate deployments can reduce total licence and support costs materially through deliberate architectural and contractual choices.

Strategy 1: Consolidate to Fewer, Larger Servers

Because GoldenGate licences on a per-processor basis, consolidating replication workloads from many small servers onto fewer large servers reduces the total processor count. A deployment spread across eight 8-core servers (32 processor licences at 0.5 factor) consolidated onto two 32-core servers (32 processor licences) costs the same. But if consolidation reduces the number of servers involved in the source-and-target count, the savings can be substantial. This is particularly relevant for hub-and-spoke topologies where intermediate relay servers add processor licence obligations.

Strategy 2: Use Oracle VM Hard Partitioning on x86

Deploying GoldenGate on Oracle VM (OVM) with CPU pinning allows organisations to count only the vCPUs assigned to the GoldenGate VMs rather than all physical cores in the server. For a 64-core server hosting a 4-vCPU GoldenGate VM, this reduces the licence count from 32 processors (64 × 0.5) to 2 processors (4 × 0.5) — a 16× reduction. The trade-off is operational overhead: Oracle VM requires dedicated management, and the hard-partitioning configuration must be maintained and documentable to survive an LMS audit.

Strategy 3: Migrate to OCI GoldenGate Managed Service

For organisations paying perpetual licence fees plus 8 percent compounding support, migrating to the consumption-based OCI GoldenGate managed service can significantly reduce total cost, particularly for non-continuous replication workloads. The managed service eliminates infrastructure management costs, removes the support escalation risk, and scales costs with actual usage. Organisations should model a five-year TCO comparison — perpetual licence plus compounding support versus OCI consumption pricing — to determine whether migration makes financial sense.

Strategy 4: Negotiate Support Caps Before Renewal

Every GoldenGate support renewal is an opportunity to negotiate a cap on the 8 percent annual support increase. Oracle will not proactively offer a cap — customers must request it explicitly, ideally during Oracle's Q4 window (March to May) when Oracle sales teams are most motivated to close agreements. A successfully negotiated 0% cap on support increases permanently eliminates the compounding cost growth; even a 3% cap versus the default 8% saves a meaningful amount over a five-year horizon on large licence estates.

Strategy 5: Evaluate Competitive Alternatives at Renewal

Oracle responds most aggressively to competitive pressure from Debezium (open source), Striim, Qlik Replicate (formerly Attunity), IBM InfoSphere DataStage, and AWS Database Migration Service. Obtaining a credible quotation from one or more competitors — even if you intend to remain on GoldenGate — provides negotiating leverage for licence discounts and support caps. Oracle account teams are authorised to offer significant one-time discounts and multi-year support caps when a competitive displacement is credible.

11. Five Negotiation Tactics

Negotiating Oracle GoldenGate contracts requires understanding Oracle's internal incentives and deploying leverage at the right moment in the procurement cycle.

Tactic 1: Negotiate in Oracle's Q4 (March–May)

Oracle's fiscal year ends May 31. During Q4, Oracle sales representatives and their managers face the strongest pressure to close deals and meet annual revenue targets. Renewals and new purchases timed for March, April, or early May consistently receive the best discounts — often 40–60% off list for GoldenGate. Organisations that allow renewals to roll automatically or renew in Q1 or Q2 leave significant savings on the table.

Tactic 2: Bundle GoldenGate with a Larger Oracle Deal

Oracle offers better pricing on GoldenGate when it is part of a larger transaction that includes Database licences, Middleware, or cloud commitments. If your organisation is already in a database renewal or cloud commitment discussion, include GoldenGate — Oracle is more likely to provide deep discounts on middleware products to protect larger database deals.

Tactic 3: Request a Formal Price Hold During Due Diligence

GoldenGate list prices have historically increased over time. When you are evaluating a purchase, request a formal price hold in writing from your Oracle account team. Price holds are typically granted for 30–60 days and lock in the current list price for calculation purposes, even if Oracle announces a price increase during your evaluation period.

Tactic 4: Challenge LMS Methodology Before Settling

If Oracle LMS identifies a licence shortfall, do not accept Oracle's initial settlement demand. Oracle's first settlement proposal is invariably based on full list price for the alleged shortfall quantity. Independent licensing advisors regularly negotiate LMS settlements to 20–40% of Oracle's opening position by challenging counting methodology, partition evidence, and edition applicability. Always obtain independent advice before engaging Oracle in a settlement discussion.

Tactic 5: Seek a Contractual Right to Terminate for Convenience

Standard Oracle GoldenGate licences are perpetual — once purchased, the licence is yours but you are contractually required to pay support annually. Requesting a right to terminate for convenience (exit the support contract without financial penalty after a minimum period) preserves your ability to migrate to a competitor or open-source alternative without paying Oracle for licences you no longer use. Oracle rarely grants this proactively but may agree as part of a larger deal.

Oracle GoldenGate licensing rewards organisations that plan carefully, engage early, and negotiate strategically. The combination of the source-and-target counting rule, compounding support increases, and cloud deployment complexity means that organisations without dedicated licensing expertise routinely pay 2–3× more than necessary. Independent advice at the procurement stage — before contracts are signed — is the most cost-effective investment any organisation can make in managing its GoldenGate estate.