Oracle virtualization licensing in 2026: which cores count.

Oracle licenses by physical core and does not accept VMware as a way to limit the count, so virtualization licensing in 2026 is a question of which cores Oracle can reach, not how many virtual machines you run.

This guide is for database, infrastructure, and procurement leaders managing Oracle on virtualized infrastructure in 2026. Pair it with Oracle on VMware and cloud and the Oracle Practice so the architecture and the contract line up.

How does Oracle count cores in a virtual estate?

Oracle licenses Database and most options by physical processor core, adjusted by a core factor. In a virtual estate the question is which physical cores the software could run on, because Oracle counts all of them.

Oracle publishes the core factor table in its Processor Core Factor Table. The factor reduces the count per core, but it does not change which cores are in scope.

Why does the virtual machine boundary not help?

A virtual machine limits the cores the workload uses at runtime, but Oracle's policy looks at where the software could run. With vMotion enabled, that is potentially every host in the cluster, not the single host the virtual machine sits on today.

• Runtime view: the virtual machine runs on one host now.
• Oracle policy view: the software could move to any linked host.
• Result: Oracle counts the full set of reachable cores.

How do shared storage and vMotion widen the count?

Shared storage and live migration link hosts into one mobility domain. Oracle treats that domain as the licensing boundary. A small Oracle footprint on a large shared cluster can therefore carry a very large counted core total.

What partitioning does Oracle actually accept?

Oracle separates partitioning into hard and soft. Only approved hard partitioning limits the licensable cores in Oracle's view. Soft partitioning, including VMware boundaries, does not, regardless of how the hypervisor enforces it technically.

How does approved hard partitioning cut the count?

Approved hard partitioning pins the software to specific cores in a way Oracle accepts. You then license only those cores. See approved hard partitioning for the practical setup.

Why does a dedicated cluster reduce risk?

A dedicated Oracle cluster keeps Oracle workloads off the shared estate. The mobility domain shrinks to that cluster, so the countable cores fall to what the cluster holds rather than the whole data center.

How do you cut Oracle virtualization cost safely?

The safe levers all shrink the set of cores Oracle can count. Isolate workloads, apply approved hard partitioning, or move to a metered cloud service. Each reduces exposure without relying on an interpretation Oracle rejects.

What protects you in an audit?

Architectural isolation in place before the audit is the strongest defense. Diagrams, host pinning, and change records that predate the audit show the boundary was real, not retrofitted under pressure.

What to do next

1. Map every host linked to Oracle workloads by storage and vMotion.
2. Count the physical cores in that full mobility domain.
3. Compare the counted cores to the cores actually running Oracle.
4. Decide between a dedicated cluster and approved hard partitioning.
5. Document the isolation with diagrams and dated change records.
6. Apply the core factor table to the isolated, reduced core set.
7. Review the architecture before any renewal or audit, not after.

Frequently asked questions

How does Oracle license software in virtualized environments in 2026?

Oracle licenses by physical processor core, and on soft partitioning hypervisors such as VMware it expects every core the software could run on to be licensed. The virtual machine boundary does not limit the count in Oracle's policy, so the cluster, not the virtual machine, sets the requirement.

What is the difference between hard and soft partitioning?

Hard partitioning physically limits the cores a workload can use in a way Oracle accepts, so you license only those cores. Soft partitioning, such as VMware vMotion boundaries, is not accepted by Oracle as a way to limit licensing, so the whole cluster is in scope.

Does Oracle accept VMware as a way to limit licensing?

No. Oracle's published policy does not recognize VMware as hard partitioning. In practice Oracle counts every host in a cluster where the software could run, and with shared storage and vMotion enabled that can mean every connected host.

How do you reduce Oracle license cost in a virtual estate?

Isolate Oracle workloads onto a dedicated cluster, use approved hard partitioning, or move to a counting model such as a cloud service that meters consumption. The goal is to shrink the set of cores Oracle can count, which dedicated clusters and approved partitioning both do.

Does Oracle count cores on AHV or Hyper V the same as VMware?

Largely yes for soft partitioning. Oracle treats Nutanix AHV and other soft partitioning hypervisors the same way it treats VMware, so the full cluster counting risk applies. Approved hard partitioning technologies are the exception, not the hypervisor brand.

What is the biggest virtualization licensing risk in an Oracle audit?

The biggest risk is the whole cluster being counted because vMotion or shared storage links hosts that were never meant to run Oracle. The defense is architectural isolation set up before the audit, because retrofitting it under audit pressure is far harder.