You license Oracle on VMware by reading the cluster claim against your signed agreement, because Oracle's partitioning policy does not recognise VMware as hard partitioning but that argument rests on policy, and contract language beats policy.
How do you license Oracle on VMware properly?
You license Oracle on VMware properly by licensing the hosts where Oracle actually runs and testing any wider claim against your contract. Oracle's position is that on a soft partitioned platform you must license every host the software could run on, which on a large cluster can mean licensing hardware that never executes an Oracle database. That position comes from a policy paper, not from most signed agreements. The proper approach starts from what the contract grants, not from what the policy asserts, and licenses accordingly.
Does Oracle recognise VMware as hard partitioning?
Oracle does not recognise VMware as hard partitioning. Its partitioning policy treats VMware, Hyper V and KVM as soft partitioning, which in Oracle's reading does not limit where a database can run and therefore argues for licensing every host in scope. This is the engine behind the cluster wide claim that inflates so many virtualization findings. Understanding that the claim is a policy position, not a contractual certainty, is the start of the buyer side response.
Why does the contract beat the policy?
The contract beats the policy because the partitioning document is not the agreement you signed. Oracle's policy papers describe how Oracle would like soft partitioning to be licensed, but they are not generally incorporated into the Oracle Master Agreement or the ordering document. Where the signed agreement does not grant a cluster wide basis, the policy cannot create one on its own. This is a contract dependent point, so it must be tested against your specific terms, but on many estates the contract simply does not support the cluster wide claim the policy asserts.
| Oracle policy claim | Buyer side contract test |
|---|---|
| License every host in the cluster | Does the contract grant a cluster wide basis? |
| VMware is soft partitioning | What does the signed agreement actually say? |
| Virtual machines can move anywhere | Have you constrained movement and isolated Oracle? |
| Full core count applies | Apply the correct core factor to the right cores |
How do you contain a cluster wide claim?
You contain a cluster wide claim by isolating Oracle workloads and controlling where virtual machines can run. Dedicating specific hosts or clusters to Oracle, and restricting the ability of Oracle virtual machines to migrate onto unlicensed hardware, narrows the population of hosts in scope. The architecture you build is itself part of the defense, because it limits where the software could run in fact, not just in policy. On a large virtual estate this single dispute can decide the whole audit, so containing it is high value work.
How does the core factor apply?
The core factor applies to the cores on the hosts that are genuinely in scope, reducing the raw core count to a processor count. A finding that both asserts a cluster wide claim and ignores the core factor compounds two overcounts at once. Applying the correct factor to the right cores, after the cluster claim has been contained, keeps the processor count tied to the hardware that actually runs Oracle rather than to the full virtual estate.
A worked example
Consider an anonymized media company whose finding licensed an entire large VMware cluster because Oracle ran on a few hosts within it. The defense isolated the Oracle workloads, showed the virtual machines were constrained, and tested the cluster wide claim against the signed agreement, which did not grant it. The correct core factor was then applied to the in scope hosts. The defensible exposure was a fraction of the opening figure. No client names, sector level example only.
The buyer moves
The buyer moves are to read the cluster wide claim against the signed contract, isolate Oracle workloads onto defined hosts, constrain virtual machine movement, and apply the correct core factor to the in scope cores. Each move narrows the claim from the whole virtual estate to the hardware that actually runs Oracle, and together they are why a virtualization finding rarely survives a buyer side review at its opening size.
Where to go next
This piece links up to the Oracle Virtualization Licensing Guide. Keep reading across the cluster:
To test a VMware cluster claim against your contract, read the Oracle Virtualization Licensing Guide or get a quote.