Oracle GoldenGate Licensing: Replication, Change Data Capture & the Application Source Metric That Multiplies Your Cost

Oracle GoldenGate Product Family: What Exists and What It Does

Oracle GoldenGate is not a single product — it is a family of products, each separately licensed, that collectively cover real-time data replication, change data capture, data transformation, and stream processing. Understanding which GoldenGate product you are using (or need) is the essential first step in GoldenGate licence compliance.

The most common compliance scenario is an organisation that purchased Oracle GoldenGate (base product) for Oracle-to-Oracle replication and subsequently used it to replicate to Kafka or Elasticsearch for an analytics use case — not realising that target type (Big Data targets) requires a separate GoldenGate for Big Data licence.

GoldenGate Licensing Model: Processors and Application Sources

Oracle GoldenGate is licensed on a processor metric — but unlike Oracle Database, which licences processors on the database server, GoldenGate licences processors on the server where GoldenGate software is installed (the GoldenGate hub or deployment host). This distinction matters because GoldenGate is often deployed on dedicated infrastructure servers separate from the source and target databases.

The base GoldenGate processor licence (at $20,000 per processor perpetual list) covers the right to run GoldenGate replication on the licensed server. However, the processor licence alone does not cover the right to replicate from an unlimited number of source databases. That is where the Application Source metric comes in.

Note that Oracle's GoldenGate pricing has evolved and varies significantly by product variant. The figures above represent indicative list prices — actual pricing in Oracle's current Price List may differ and should be verified against Oracle's published Global Price List. Oracle also regularly offers GoldenGate in bundles, as part of EA structures, and on OCI's subscription model at pricing that differs substantially from perpetual list.

The Application Source Metric: How It Is Calculated

The Application Source metric is the GoldenGate licensing element that creates the most compliance complexity. An Application Source is defined as each unique combination of source database instance and database type that GoldenGate captures changes from. The counting rules are specific:

• Each Oracle Database instance that GoldenGate captures from (via an Extract process) counts as one Application Source
• Each non-Oracle database instance that GoldenGate captures from counts as one Application Source under the GoldenGate for Non-Oracle Databases licence
• A single database instance that is both a source (Extract) and a target (Replicat) counts as one Application Source — the target side does not add to the Application Source count
• Bidirectional replication (active-active Oracle-to-Oracle) where both sides are sources counts as two Application Sources (one for each direction's source database instance)
• Development, test, and DR environments that GoldenGate connects to count as Application Sources; they are not automatically excluded from the Application Source count

The Application Source metric interacts with GoldenGate's product variants in a compound way. If you have GoldenGate base product licences with three Application Sources (Oracle-to-Oracle) and then add a GoldenGate for Big Data stream to Kafka from the same source Oracle databases, you need additional GoldenGate for Big Data Application Source licences — even though the source Oracle database is already licensed as an Application Source under your base GoldenGate entitlement. Each GoldenGate product variant maintains its own Application Source count.

GoldenGate for Big Data: The Most Commonly Under-Licensed Product

Oracle GoldenGate for Big Data is the product variant most frequently found under-licensed in Oracle compliance reviews. The explanation is straightforward: enterprises purchased GoldenGate for Oracle-to-Oracle replication (the base product) and then, as their data architecture evolved, began using GoldenGate to feed analytics platforms — Kafka, Confluent, Elasticsearch, MongoDB, or cloud data lakes. That usage requires GoldenGate for Big Data, which is a separately licensed product with its own Application Source count.

GoldenGate for Big Data is frequently used for the following scenarios that commonly go unlicensed:

Each of these scenarios requires a GoldenGate for Big Data licence, with Application Source licences for each Oracle source database instance feeding the Big Data targets. In an enterprise with 10 Oracle source databases feeding Kafka topics (a common data platform architecture), the GoldenGate for Big Data requirement is 10 Application Source licences — a licence obligation that was commonly not known to exist until Oracle's LMS team surfaced it.

How Oracle LMS Detects GoldenGate Usage

Oracle GoldenGate does not leave traces in the Oracle Database data dictionary in the same way that database options do. Instead, Oracle's LMS team detects GoldenGate usage through a combination of file-system inspection of GoldenGate installation directories, GoldenGate parameter file analysis, and GoldenGate Manager and Extract process logs. When Oracle's USMM is deployed, it also detects GoldenGate binary presence on the server.

The specific detection points Oracle LMS uses for GoldenGate are:

Common GoldenGate Compliance Gaps: What Oracle Finds in Audits

Oracle LMS GoldenGate audit findings cluster around a consistent set of compliance gaps. Based on our experience representing enterprises through GoldenGate-related Oracle audit engagements, the most frequent findings are:

• Unlicensed GoldenGate for Big Data usage — most common; base GoldenGate product licences used for Kafka/Elasticsearch/cloud target replication that requires GoldenGate for Big Data
• Application Source undercount — licence entitlement covers fewer Application Sources than the number of Extract configurations in the GoldenGate deployment; typically occurs after GoldenGate scope expanded beyond the original use case
• GoldenGate for Non-Oracle Databases unlicensed — GoldenGate base product used for heterogeneous replication (Oracle to SQL Server, SQL Server to Oracle) without the Non-Oracle Database variant licence
• GoldenGate Veridata unlicensed — Veridata installed and used for data consistency validation without a Veridata licence; typically deployed by DBAs validating GoldenGate replication consistency during migration projects
• Processor count undercount on GoldenGate hub — GoldenGate deployed on a server with more processors than are covered by the GoldenGate processor licence entitlement

Our Oracle Audit Defence team has challenged GoldenGate audit findings where Oracle's Application Source count was inflated by including decommissioned Extract configurations that were no longer active at the time of audit. Oracle's position that historical Extract configurations create ongoing licence obligations is not always contractually correct — the entitlement obligation typically runs from when the usage occurs, not forward-looking from decommissioned configurations.

Oracle GoldenGate on OCI: GGS and Cloud Licensing

Oracle GoldenGate Service (GGS) is Oracle's managed cloud version of GoldenGate available on OCI. GGS eliminates the on-premises GoldenGate infrastructure licensing model — there are no processor licences or Application Source perpetual licences. Instead, GGS is licensed per OCPU-hour via OCI Universal Credits, with pricing based on the GoldenGate service tier and the data volume processed.

For enterprises currently running GoldenGate on-premises with significant licence spend, GGS presents a genuine total-cost-of-ownership alternative that should be evaluated during EA or support renewal negotiations. Our Oracle Cloud Advisory team has conducted GGS vs. on-premises GoldenGate comparisons for enterprises with 10–50 Application Sources, finding that GGS is cost-effective for organisations with variable replication workloads and where OCI Universal Credits are already in use for other Oracle cloud services.

The catch: migrating to GGS does not automatically eliminate existing on-premises GoldenGate perpetual licence obligations. Perpetual licences are owned assets with ongoing support costs. Transitioning to GGS while maintaining on-premises licence support payments creates a dual-cost scenario during the transition period. Oracle's support reduction advisory — available through our Support Cost Reduction service — identifies strategies to terminate on-premises GoldenGate support obligations when transitioning to GGS.

Right-Sizing GoldenGate Entitlement: Negotiation Framework

For enterprises with identified GoldenGate compliance gaps — whether discovered proactively or surfaced through an Oracle LMS audit — the resolution path depends on whether the gap is historical (usage already occurred) or forward-looking (you need to expand GoldenGate usage). The approaches differ:

Forward-looking compliance gap resolution: If you need additional GoldenGate product variants or Application Sources for future use, negotiate as part of a broader Oracle technology renewal. GoldenGate discounts of 60–70% off list price are achievable in EA structures where GoldenGate is bundled with Oracle Database EE, Java SE, or other technology products. Oracle's sales teams are motivated to include GoldenGate in EA commitments as it extends product stickiness. Use this leverage.

Historical compliance gap resolution (audit finding): Challenge Oracle's Application Source count and usage duration claims with forensic evidence. Verify whether decommissioned Extract configurations should be included in the Application Source count. Review whether your Master Agreement or any ULA covered GoldenGate products during the period of alleged non-compliance. The Fortune 500 Bank EA Restructure case study includes a GoldenGate licence rationalisation component where historical Application Source claims were reduced through contract term analysis.

Contact our licensing advisory team for a confidential assessment of your GoldenGate position before your Oracle ULA renewal or audit response deadline.