Get Oracle Licensing Intelligence
Join enterprise IT leaders receiving our monthly advisory on Oracle audit tactics, licensing changes, and compliance risk management.
By Fredrik Filipsson · Oracle Licensing · GoldenGate Audit Risks · Compliance Defence · Updated 2026
01 Processor & Core Counting Risks
Perhaps the most frequent audit issue is incorrect calculation of required licences. This happens when the Oracle core factor is not applied correctly, or is applied when it should not be, leading to either over-counting or under-counting.
Miscounting Processors and Cores
Over-Licensing Risk
An organisation deploys GoldenGate on an Intel server and forgets to apply the 0.5 core factor, assuming 1 core = 1 licence. On an 8-core server, this means buying 8 licences when only 4 are required (8 x 0.5 = 4). While over-licensing is not a compliance violation, it wastes budget unnecessarily.
Under-Licensing Risk
Others misunderstand rounding rules and under-licence. For example, 6 cores x 0.5 = 3 licences, but if someone mistakenly calculates 2.5 and rounds down, they are under-licenced. Oracle's formula requires you to always round up. Document your calculations for each server.
Ignoring NUP Minimums
In rare cases where Named User Plus (NUP) is used for GoldenGate, Oracle requires a minimum of 25 Named Users per processor. If you have 30 users on a 4-core server, the minimum would be 25 x (cores x factor). Not meeting those minimums is non-compliant even if actual users are fewer. While NUP for GoldenGate is unusual, it is worth noting.
02 Virtualisation Traps (VMware & Others)
Virtualisation is the single biggest compliance trap with Oracle software including GoldenGate. Many organisations run GoldenGate in virtual environments such as VMware vSphere, not realising Oracle's policy requires licensing far beyond the resources assigned to their VM.
Oracle's VMware Policy
Oracle treats VMware as soft partitioning, requiring licensing of all physical cores in any cluster where Oracle software could run, not just the portion the VM uses. If vMotion is enabled, Oracle asserts that the VM could migrate to any host in the cluster, requiring licensing of every host.
Mitigation Strategies
Physically Segment Oracle Workloads
Create a separate VMware cluster dedicated to Oracle DB and GoldenGate with limited hosts, separate from your general virtualisation farm. This caps the "blast radius" of Oracle's licensing claim.
Use Oracle-Approved Hard Partitioning
Oracle VM Server, Oracle Linux KVM with hard partitioning, or Solaris Zones are formally recognised by Oracle as hard partitioning. These allow licensing only the resources assigned to the partition. Oracle does not officially recognise VMware as hard partitioning.
Document Affinity Rules
Pin GoldenGate VMs to specific hosts using VMware DRS affinity rules. While Oracle may not formally accept this in policy, it can serve as a negotiation point during audit discussions and demonstrates intent to contain the deployment.
03 Cloud Calculation Errors
A common mistake is applying on-premises rules to cloud deployments or vice versa. Oracle uses different licensing rules in authorised cloud environments (AWS, Azure, GCP).
The Cloud vCPU Rule
In authorised public clouds, Oracle's standard policy is 2 vCPUs = 1 processor licence (for most instances with hyper-threading). The on-premises core factor table does not apply.
Correct Calculation
8 vCPU Azure VM divided by 2 = 4 processor licences. This is the correct method in authorised public clouds.
Common Error: Using Core Factor in Cloud
An engineer applies 8 vCPU x 0.5 core factor / 2 = 2 licences. This is wrong. The core factor does not apply in cloud. The correct answer is 4 licences.
Common Error: Over-Licensing
Assuming 8 vCPUs = 8 licences (not knowing about the 2:1 rule). This wastes budget paying double what is required.
Vendor Shield: Oracle Audit Defence
Facing an Oracle audit or unsure about your GoldenGate licensing? Get independent compliance assessment before Oracle sets the agenda.
04 Licensing Scope & Edition Misuse
Unlicensed Targets & Sources
A common scenario: GoldenGate is set up to capture from or deliver to a database that the team did not realise needed its own licence. You might licence the primary database's GoldenGate server but forget to licence the secondary (target) server. In an audit, Oracle will ask for installation details. If GoldenGate binaries are installed on that target server without a corresponding licence, that is a compliance gap. Any environment where GoldenGate binaries are installed and used should correspond to a licence entitlement.
Wrong Edition Licence
Oracle expects the correct GoldenGate licence type for the use case. Several editions exist for different scenarios.
GoldenGate (for Oracle Database)
Covers Oracle-to-Oracle replication only. If you use this to replicate from Oracle DB into Kafka or another non-Oracle target, Oracle could argue you need the Big Data edition for those processors.
GoldenGate for Non-Oracle (Heterogeneous)
Required when replicating to or from non-Oracle databases (SQL Server, PostgreSQL, MySQL, etc.). If your configuration was originally Oracle-to-Oracle and you later added a SQL Server target, you need the non-Oracle licence at that point.
GoldenGate for Big Data
Required for streaming to Kafka, HDFS, or other big data platforms. Using the standard Oracle edition for big data targets is technically non-compliant.
Non-Production Environments Unlicensed
Teams sometimes spin up GoldenGate in dev or test environments without including it in licensing counts, assuming only production needs licensing. Oracle licences do not differentiate by environment. A deployment is a deployment. An audit will request details of all environments.
05 Version, Feature & Audit Data Risks
GoldenGate Version & Feature Misuse
Management Pack for GoldenGate
Oracle offers a separate management pack for monitoring GoldenGate via Oracle Enterprise Manager. This is a separate licence. Enabling it without purchasing the pack is a violation. If Enterprise Manager is configured to monitor GoldenGate processes, verify your licence entitlement.
Version Upgrades & Support Lapse
If you upgrade GoldenGate to a newer major version, ensure your support is active. A version released after your support lapsed might be considered unlicensed. Your licence grants rights only up to the version available during your active support period. Stay current with support or remain on versions you have the right to use.
Embedded Technology
Monitoring tools or custom solutions that embed GoldenGate technology may also require licensing. Any use of GoldenGate binaries or capabilities needs to be accounted for in your entitlements.
Audit Data Gathering Mistakes
During an audit, Oracle will provide scripts or requests for data. For GoldenGate, they may ask for inventory or logs. Mistakes in how this data is gathered or reported can inadvertently expose you to compliance issues.
06 Compliance Best Practices & Audit Defence
Preparation and proactive compliance management are key. Oracle's LMS auditors are thorough, and GoldenGate licensing is less familiar to some IT teams than database licensing. The element of surprise can be higher.
Conduct Regular Internal Licence Audits
Check that every GoldenGate installation is accounted for in your licence counts. Review all environments, production, development, test, staging, DR, against entitlements. Conduct these at least annually, preferably semi-annually for large estates.
Maintain Accurate Documentation
Keep records of where GoldenGate is installed, how many cores or vCPUs it uses, what type of licence covers it, and how you calculated the requirement. This documentation is invaluable in audit defence. It demonstrates diligence and controls the narrative.
Assess Licensing Impact Before Architectural Changes
Have licensing experts assess the impact before making changes like expanding a VMware cluster, adding a new replication target, moving to cloud, or adding a non-Oracle database to the GoldenGate topology. Reactive discovery is always more expensive than proactive planning.
Be Conservative About What Is "Free"
Unless explicitly documented (like the 10-day failover rule, or GoldenGate Free with its constraints), assume you need a licence. Oracle's default position in an audit is that any installation requires entitlements. Better to confirm before deploying than to discover gaps under audit pressure.
Engage Independent Licensing Experts
GoldenGate licensing is niche and evolving. Independent advisors bring current knowledge of Oracle's policies, audit tactics, and negotiation approaches. They can validate your licence position, identify exposure before Oracle does, and manage the audit process end-to-end. See our Oracle Licence Management Services.
Control Audit Communications
If an Oracle audit notice arrives, channel all communications through a single point of contact (procurement or legal). Never submit data without review. Only provide what the contract scope requires. Our Oracle Audit Defence Service manages this process to protect your commercial position.
Vendor Shield: Oracle Licence Management
Need a GoldenGate licence assessment or facing an Oracle audit? Our specialists know every compliance trap.
📂 Oracle Licensing Case Studies
Oracle Licensing Assessment Case Studies → Oracle ULA Case Studies: How We Save Enterprises Millions → Oracle Support Reduction Case Studies → Complete Case Studies: All Vendors →📄 GoldenGate & Oracle Licensing Deep-Dives
Oracle GoldenGate Licensing Overview → GoldenGate Licence Optimisation Strategies → GoldenGate Licensing for HA & Disaster Recovery → Oracle Licensing in VMware Environments: Complete Guide → Oracle Audit Survival Guide for CIOs → Oracle Database Licensing: Comprehensive DBA Guide → Oracle Middleware Licensing for CIOs → Oracle Support Cost Reduction Strategies → Oracle Cloud Licensing Guide →Frequently Asked Questions
Miscounting processors and cores is the most frequent issue. This includes not applying Oracle's core factor correctly (or applying it in cloud environments where it does not apply), failing to round up, and not accounting for all servers where GoldenGate binaries are installed. Virtualisation-related under-licensing (especially VMware) is the second most common, and typically the most financially devastating finding.
Yes. Oracle's policy treats VMware as soft partitioning. If vMotion is enabled (allowing VMs to migrate between hosts), Oracle asserts that all physical cores in the entire cluster must be licensed, not just the cores assigned to the GoldenGate VM. The most effective mitigation is creating a separate, dedicated VMware cluster for Oracle workloads with limited hosts, thereby capping the licensing exposure to that smaller cluster.
Yes. Oracle licences do not differentiate by environment. Any deployment is a deployment. If GoldenGate is installed and used in dev, test, staging, or DR, it requires licensing. Options include using GoldenGate Free in dev/test (with its limitations: 20GB data, Oracle-to-Oracle only), budgeting for non-production licences, or carefully managing licence allocation so that you never exceed your total entitlement count across all environments simultaneously.
In authorised public clouds (AWS, Azure, GCP), Oracle uses a 2 vCPU = 1 processor licence rule for most instance types. The on-premises core factor table does not apply. So an 8-vCPU cloud instance requires 4 licences (8 / 2), not 8 x 0.5 = 4 (which happens to give the same result for Intel x86 but would be wrong methodology), and definitely not 8 licences. Be aware of which rules apply in which environment to avoid both under-licensing and unnecessary spend.
This is a common trap. If you originally licensed GoldenGate for Oracle-to-Oracle replication and later add a SQL Server target, you likely need GoldenGate for Non-Oracle licences. If you add a Kafka or HDFS target, you may need GoldenGate for Big Data licences. Each architectural change should trigger a licensing review. Ensure your licence inventory is updated whenever the GoldenGate topology changes. Oracle auditors will compare actual usage against entitled editions.
Yes. The Management Pack for GoldenGate (monitoring via Oracle Enterprise Manager) is a separate licence. If Enterprise Manager is configured to monitor GoldenGate processes and you do not have the pack licensed, that is a compliance violation. Many organisations avoid it, but if your OEM setup includes GoldenGate monitoring targets, verify your entitlement.
Do not panic, and do not respond without expert guidance. Channel all communications through a single point of contact (procurement or legal). Never submit data to Oracle without independent review. Errors in reported server specs can inflate Oracle's licence calculation. Engage independent Oracle audit defence advisors who can manage the process, verify data accuracy, control audit scope, and protect your commercial position through negotiation.
GoldenGate Free has significant limitations: it supports only Oracle-to-Oracle replication with a 20GB data limit and other constraints. It is primarily designed for development, testing, and evaluation. For production workloads requiring heterogeneous replication, larger data volumes, or enterprise features, you will need the commercially licensed editions. However, GoldenGate Free can be useful for non-production environments to avoid additional licence costs where its limitations are acceptable.
Oracle Audit Defence
Service
Oracle Licence Management
Service
Oracle Contract Negotiation
Service
Oracle ULA Optimisation
Service
Oracle Advisory Services
Service
GoldenGate Licensing Overview
GoldenGate
Licence Optimisation Strategies
Optimisation
Database Licensing: DBA Guide
Database
Middleware Licensing for CIOs
Middleware
Support Cost Reduction
Support
Don't Wait for Oracle to Find Your GoldenGate Gaps
Whether you are facing an Oracle audit, planning a GoldenGate deployment, or need an independent compliance assessment, Redress Compliance delivers vendor-independent advisory with a track record of saving Fortune 500 enterprises millions.
Also managing Java, middleware, database, or ULA contracts? We cover the full Oracle stack. All Oracle Advisory Services →