Oracle still treats VMware as a soft partition. Broadcom now controls the platform. The licensing posture, the audit risk, and the buyer side options all shifted in the same quarter.
Oracle treats VMware as soft partitioning and claims the whole estate, but that claim lives in policy, not your contract. Here is how to cap the real exposure.
Oracle classifies VMware vSphere as soft partitioning, which under its policy means the partition cannot reduce what you owe. The practical claim is that every physical core where an Oracle virtual machine could run must be fully licensed.
This rule does not appear in the Oracle ordering document or the master agreement. It lives in a separate Oracle Partitioning Policy that Oracle itself labels as educational and not contractual.
The core factor that converts physical cores to licenses sits in the Oracle Processor Core Factor Table. The processor metric itself is defined in the Oracle pricing and licensing pages.
Start from the cores running Oracle, then test how far Oracle argues the boundary extends. The answer decides the bill.
How the licensable footprint changes with isolation
| Architecture | Oracle policy claim | Defensible footprint |
|---|---|---|
| Oracle VMs mixed across vCenter | Every host in vCenter | Weak, very large exposure |
| Single dedicated Oracle cluster | All hosts in that cluster | Cluster cores only |
| Dedicated hosts with affinity rules | Contested | Pinned hosts, with evidence |
| Physical or hard partitioned servers | Those servers only | Certain and minimal |
From vSphere 6.0 onward, vMotion can move a VM across linked vCenters. Oracle uses that capability to argue the whole estate is in scope, even where no Oracle VM has ever run on a given host.
White Paper · Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
Broadcom completed its VMware acquisition and moved the portfolio to subscription bundles under VMware Cloud Foundation. Many buyers saw renewal quotes rise sharply.
Higher VMware cost changed the math on where Oracle should live. Some buyers consolidated Oracle onto fewer, isolated hosts. Others moved Oracle to engineered systems or to a cloud with clearer counting rules.
The standard reseller and account team line is that VMware makes you license the entire virtual estate, so resistance is pointless. We disagree. In roughly 30 to 40 disputes we reviewed, the policy claim collapsed under the contract every time the buyer held the line, because the partitioning document is not a contract term. The buyer side move is to isolate Oracle, log where it runs, and refuse to treat the policy as binding. Conceding the whole estate hands Oracle leverage it never bought.
Defense is evidence plus architecture. The buyer who can show deliberate isolation, dated before contact, negotiates from a far stronger seat.
Give the measured count from where Oracle actually runs, with the supporting logs. Do not volunteer the whole vCenter inventory. Answer the question asked, in writing, and nothing wider.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The partitioning policy is a claim Oracle makes, not a clause you signed. Treat it that way and the number moves.
No, Oracle's policy claims it but the contract does not. The all hosts position lives in the Oracle Partitioning Policy, which Oracle labels educational and not contractual, so it is a negotiating claim rather than an enforceable term.
Oracle treats VMware vSphere as soft partitioning. That means Oracle's policy position is that the hypervisor does not reduce the cores you must license, unlike approved hard partitioning methods such as Oracle VM with pinned cores or physical separation.
Yes, you can defend a count based on where Oracle actually runs when you isolate the workload and keep evidence. A dedicated cluster, host affinity rules, and placement logs support counting only those cores.
vSphere 6.0 added cross vCenter vMotion, which Oracle uses to argue that a VM could move anywhere in the estate. The counter is that capability is not usage and logs show the real placement boundary.
Broadcom moved VMware to subscription bundles after its acquisition, and many buyers saw renewal costs rise. The higher VMware price changed where Oracle workloads should sit and pushed some buyers to isolate or migrate Oracle.
A dated architecture memo written before any Oracle contact is the strongest evidence. It shows that isolation was deliberate, which undercuts the argument that Oracle could have run anywhere across the estate.
No, you should answer audit questions narrowly and in writing. Volunteering the entire vCenter inventory hands Oracle the data it needs to argue the widest possible scope, so provide only the measured count from where Oracle runs.
Moving Oracle to an authorized cloud replaces the VMware counting argument with the cloud vCPU rules in Oracle's cloud licensing policy. It can simplify counting, but you must model the new metric and any contract terms before you commit.
A buyer side reference on Oracle support, the partition policy posture on VMware after Broadcom, the OCI and AWS RDS options, and the audit defense plan.
Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying Oracle estates on VMware. No Oracle influence. No sales kickback.
Oracle ULA Decision Framework
Open the white paper in your browser. Corporate email only.
Open the Paper →Oracle's partition policy did not move when Broadcom bought VMware. The cost line moved. The buyer side response is to read the two contracts independently and to fund the migration plan from the VMware renewal saving.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Partition policy posture, audit defense plans, OCI BYOL migration math, AWS RDS positioning, and the VMware renewal lever across every Oracle engagement we run.
Read it free in your browser. The moves we use across Oracle Database, Java and ULA estates. Read it free. No email wall to read it.
Opens in your browser. No sign up required to read it.
