Oracle treats VMware as soft partitioning, so it counts every core a database could ever reach, not the cores it runs on today. The disciplined buyer side response.
Oracle counts an entire VMware estate against your database licenses unless you physically isolate it. That single rule drives most of the cost surprise on virtualized Oracle.
VMware is soft partitioning in Oracle's view. The database does not need to run on a host for Oracle to count that host's cores. The right to migrate is enough.
This guide walks the counting rule, the version escalation, the containment moves that hold, and the cloud math. Read it with the Oracle Database licensing guide.
Oracle counts every physical core where an Oracle database could run, not where it runs today. Because VMware lets a virtual machine live migrate, Oracle treats the whole reachable estate as licensable. Oracle states its approved methods in the Oracle Partitioning Policy.
The policy is a contract position, not a technical limit. It means the boundary you draw in VMware does not bind Oracle unless it matches a method Oracle approves.
Hard partitioning lets you license a subset of a server. Soft partitioning does not. VMware sits firmly in the soft category.
Wherever a database VM can vMotion, Oracle counts the cores. A shared cluster or a shared vCenter therefore becomes one reachable pool. Apply the published multipliers from the Processor Core Factor Table to the full pool, not the pinned hosts.
Each VMware release that broadened live migration broadened Oracle's reachable scope. Oracle's audit teams cite the version to argue the largest defensible boundary.
The version is not the problem. The shared scope is. A modern vSphere estate with one flat vCenter gives Oracle the widest claim, so the fix is architectural separation, not a downgrade.
Containment means cutting the reachable pool down to a boundary Oracle accepts. Only physical and licensing separation holds. Configuration rules inside vSphere do not.
Containment approaches and Oracle's stance
| Approach | Oracle stance | What Oracle counts |
|---|---|---|
| Shared cluster, host affinity (DRS) | Rejected | Every core in the vCenter |
| Dedicated Oracle cluster | Accepted in practice | Cores in that cluster |
| Separate vCenter and SSO domain | Strongest soft boundary | Cores in the isolated estate |
| Physical isolation, capped sockets | Accepted | The capped sockets only |
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
On authorized clouds the metric changes from reachable cores to a fixed vCPU conversion, which is often cheaper and always more predictable. Oracle sets the rule in its Cloud Licensing Policy.
The standard advice from many infrastructure teams is that DRS host affinity rules will pin Oracle to a few hosts and cap the license count. We disagree. In roughly 30 of the 50 virtualized estates we reviewed across 2024 and 2025, Oracle rejected affinity rules in the audit because the VM could still be moved by an administrator, so the reachable pool stood. The buyer side move is to build a physically separate Oracle cluster on capped sockets, in its own vCenter, and to treat configuration rules as convenience, not as a licensing boundary that Oracle will honor.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The Oracle number on a VMware estate is the size of the cluster Oracle can reach, not the size of the workload you run. Shrink the reach and you shrink the bill.
The checklist below sequences the measurement and the isolation ahead of an Oracle renewal or audit.
Oracle counts every host a database VM can reach through vMotion, not only the hosts it runs on. VMware is soft partitioning, so the reachable pool is the licensable boundary unless you physically isolate the estate.
No. VMware is soft partitioning in Oracle's view, so it is not on the approved hard partitioning list. The approved methods are physical domains and capped partitions, which VMware does not provide.
Not reliably. Oracle commonly rejects DRS host affinity as a licensing boundary because an administrator can move the VM. Only physical separation or a separate vCenter holds in an audit.
The gap between pinned hosts and the full reachable pool is commonly 3 to 8 times. On a large shared vCenter the difference can run into seven figures, which is why isolation pays.
Yes. Isolating the Oracle estate in its own vCenter and SSO domain cuts the reachable pool to that estate. It is the strongest soft boundary short of fully separate hardware.
On authorized clouds the rule converts vCPU to processors. Two vCPU equal one processor when hyperthreading is on, which replaces the reachable core argument with a fixed and predictable count.
Often yes. OCI uses a more favorable BYOL conversion and removes the reachable core problem entirely. The right answer depends on the workload, so model BYOL across OCI, AWS, and Azure.
Redress maps the reachable pool, designs the contained estate, and runs the renewal on the measured position. Every engagement is led on the buyer side by a former Oracle licensing executive.
Redress runs Oracle on VMware advisory inside the Vendor Shield subscription, the Renewal Program, and the Benchmark Program, led on the buyer side by a former Oracle licensing executive.
Read the related Oracle services page, the Oracle knowledge hub, the benchmarking page, and the contact page.
A buyer side reference on the Oracle Unlimited License Agreement decision. Certification scope, the exit path, audit posture, support strategy, and the commercial levers that still hold at renewal.
Used across more than five hundred enterprise software engagements. Independent. Buyer side. Built for Oracle customers running the next renewal cycle.
Open the white paper in your browser. Corporate email only.
Open the Paper →
Renewal in twelve months. Audit notice in the inbox. RFP on the desk. We start where you are.
VMware core counting rules, vMotion scope, containment moves, OCI and BYOL math, and audit defense intelligence from every Oracle engagement we run on the buyer side.
Read the full white paper free in your browser. No PDF buried in your inbox, and no follow up sales call unless you ask for one.
Read the white paper free →Opens on the next screen. Read it now, no download required.
