Oracle treats VMware as soft partitioning, so it counts every physical core in the cluster, and often the whole vCenter, not the two hosts your database runs on. This paper shows the exposure math and the buyer side defense that holds.
Oracle on VMware is the single largest source of license exposure we see in Oracle estates. The database may run on two hosts, yet the audit claim can cover the whole cluster, or the whole vCenter, at $47,500 per processor plus 22 percent annual support.
The reason is classification. Oracle calls VMware vSphere soft partitioning and counts every physical core an Oracle virtual machine could reach, not the cores it uses. Since vSphere 6.0, that reach extends across clusters and linked vCenter servers.
This white paper walks the counting rules, the worked cost math on a representative estate, why host affinity does not satisfy Oracle, and the contract based defense. The decisive point is that the partitioning policy is not a contract document, so your signed agreement, not the policy, controls.
Yes, Oracle Database runs on VMware and Oracle supports the software itself, but Oracle does not recognize VMware as a way to limit licensing. VMware vSphere is classified as soft partitioning, so Oracle counts the physical cores in the environment rather than the cores the database actually uses.
Oracle's audit position is that every physical core an Oracle virtual machine could run on must be licensed. On an eight host cluster of 32 core hosts at the 0.5 Intel core factor, that is 128 processor licenses, even when the database runs on two hosts. The exposure can extend to the whole vCenter.
No, the Oracle partitioning policy is not a contract document. Oracle states it is for educational purposes and may not be incorporated into a contract. Your Oracle Master Agreement and order documents govern your obligations, and where they conflict with the policy, the signed agreement controls.
No, Oracle rejects DRS host affinity rules and VM pinning at audit as soft controls the customer can change at any time. The reliable technical defense is to isolate Oracle on a separate physical cluster with its own storage and no vMotion path to the rest of the estate.
Isolate Oracle onto dedicated hardware to remove the migration reach Oracle relies on, read your contract before the policy, control the audit data you provide, and price the 22 percent annual support that rides on every conceded processor. Estates that isolate and hold the contract line settle well below the opening claim.
Yes, since vSphere 6.0 a running virtual machine can move across linked vCenter servers, and Oracle uses that reach to argue the licensable boundary spans every connected host across data centers. Removing the migration path between Oracle hosts and the wider estate is what limits the claim.
Independent. Buyer side. The advisory firm enterprise software vendors do not want you to hire.
What we are seeing across 500+ enterprise clients, delivered monthly. Free.
