Oracle's licence audits are rigorous, and GoldenGate deployments are increasingly scrutinised. This guide covers the most common compliance pitfalls — from processor miscounting and virtualisation traps to cloud calculation errors, unlicensed targets, edition misuse, and non-production exposure — plus best practices to avoid them.
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 shouldn't be), leading to either over-counting or under-counting.
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 × 0.5 = 4). While over-licensing isn't a compliance violation, it wastes budget unnecessarily.
Others misunderstand rounding rules and under-licence. For example, 6 cores × 0.5 = 3 licences, but if someone mistakenly calculates 2.5 and rounds down, they're under-licenced. Oracle's formula requires you to always round up. Document your calculations for each server.
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 × (cores × factor). Not meeting those minimums is non-compliant even if actual users are fewer. While NUP for GoldenGate is unusual, it's worth noting.
Virtualisation is the single biggest compliance trap with Oracle software including GoldenGate. Many organisations run GoldenGate in virtual environments (e.g., VMware vSphere), not realising Oracle's policy requires licensing far beyond the resources assigned to their VM.
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.
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.
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. Note: Oracle does not officially recognise VMware as hard partitioning.
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.
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).
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. This means:
8 vCPU Azure VM ÷ 2 = 4 processor licences
An engineer applies 8 vCPU × 0.5 core factor ÷ 2 = 2 licences. This is wrong — the core factor doesn't apply in cloud. The correct answer is 4 licences.
Assuming 8 vCPUs = 8 licences (not knowing about the 2:1 rule). This wastes budget paying double what's required.
Facing an Oracle audit or unsure about your GoldenGate licensing? Get independent compliance assessment before Oracle sets the agenda.
Oracle Audit Defence →A common scenario: GoldenGate is set up to capture from or deliver to a database that the team didn't realise needed its own licence. For instance, 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's a compliance gap. Any environment where GoldenGate binaries are installed and used should correspond to a licence entitlement.
Oracle expects the correct GoldenGate licence type for the use case. Several editions exist for different scenarios:
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.
Required when replicating to/from non-Oracle databases (SQL Server, PostgreSQL, MySQL, etc.). If your configuration originally was Oracle-to-Oracle and you later added a SQL Server target, you'd need to add the non-Oracle licence at that point.
Required for streaming to Kafka, HDFS, or other big data platforms. Using the standard Oracle edition for big data targets is technically non-compliant.
Teams sometimes spin up GoldenGate in dev or test environments without including it in licensing counts, assuming only production needs licensing. Oracle licences don't differentiate by environment — a deployment is a deployment. An audit will request details of all environments.
Use Oracle GoldenGate Free in dev/test if your use case fits its limitations (20GB data, Oracle-to-Oracle only). Alternatively, include at least some licensing for non-prod in your budget. If non-prod usage is intermittent, you may shuffle licences between prod and test (as long as you're not running beyond total licence count concurrently).
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. Many organisations avoid it, but if Enterprise Manager is configured to monitor GoldenGate processes, verify your licence entitlement.
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.
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.
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.
If you provide Oracle with a list of server specs and one server's core count is reported incorrectly high, Oracle will calculate a larger licence requirement based on that inflated number. Always double-check any audit response data for accuracy before submitting. Have multiple team members review the data, and cross-reference against your own asset management records.
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.
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.
Keep records of where GoldenGate is installed, how many cores/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.
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.
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.
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.
If an Oracle audit notice arrives, channel all communications through a single point of contact (procurement/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.
Need a GoldenGate licence assessment or facing an Oracle audit? Our specialists know every compliance trap.
Oracle Licence Management →Whether you're 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 →