Oracle's Partitioning Policy: The Foundation
Oracle's partitioning policy is the commercial foundation of every virtualisation licensing decision. The policy determines whether Oracle Database licences are calculated based on the physical processors in the host server, or based on a smaller, partitioned allocation of processors within the host.
Oracle recognises two categories of partitioning: hard partitioning and soft partitioning.
Hard partitioning uses hardware or operating system mechanisms that Oracle considers sufficiently rigid to prevent Oracle workloads from accessing additional processors without a reconfiguration. When hard partitioning is properly configured and certified by Oracle, the enterprise may licence only the partitioned processor allocation — not all host processors.
Soft partitioning uses virtualisation mechanisms that, in Oracle's view, allow Oracle workloads to potentially access additional host processors — either through live migration, dynamic resource allocation, or similar mechanisms. Oracle requires all physical host processors to be licensed when soft partitioning is in use, regardless of what the Oracle workload actually uses.
Oracle's approved hard partitioning technologies are a short and specific list. Oracle VM Server for x86 with hard-pinned vCPUs is on it. VMware vSphere, Microsoft Hyper-V, and most other mainstream virtualisation platforms are not.
Oracle's partitioning policy is the single most significant source of unplanned Oracle licensing cost we encounter in enterprise assessments. The majority of enterprises running Oracle on VMware are licensing compliance risks — not because they are wilfully non-compliant, but because the VMware deployment decision was made without Oracle licensing input.
The VMware Licensing Problem
VMware vSphere is classified by Oracle as a soft partitioning technology. This has been Oracle's stated position since at least 2007 and has been consistently enforced in Oracle LMS audit findings. The implications for enterprise licensing costs are substantial.
All Host Processors Must Be Licensed
When Oracle Database — any edition, any version — is deployed in a VMware virtual machine, Oracle requires all physical processor sockets on the physical host to be licensed. The vCPU allocation of the virtual machine is irrelevant for licensing purposes. A 2-vCPU Oracle VM on a 4-socket, 64-core physical host requires 4 processor licences — one per physical socket, subject to the Oracle core factor table.
vMotion and Live Migration Compound the Problem
Oracle further requires that all processors in the vSphere cluster to which the Oracle VM belongs must be licensed, if the VM is configured for vMotion (live migration). Oracle's position is that a VM that can migrate to any host in the cluster might — at any point — access the processors of any host in the cluster. A vSphere cluster with 10 hosts, each with 2 sockets, creates a potential obligation to licence 20 processors for a single Oracle Database VM.
This interpretation is contested by some enterprise buyers. Oracle's LMS auditors, however, consistently apply it. The safest approach is to either licence all processors in the cluster, or to isolate Oracle VMs to dedicated hosts and disable vMotion for those specific VMs — a configuration that most IT teams resist as it defeats the purpose of their VMware investment.
The Audit Exposure
Oracle's LMS audits of VMware environments consistently find significant underpayment — enterprises that have deployed Oracle Database in VMware VMs and licensed only the vCPUs, or only one socket, rather than all physical host sockets. These audit findings frequently result in demands for substantial back-payment of licence fees plus support costs. See our audit defence guide: Oracle Audit Defence: What to Do When You Get the Letter.
Oracle VM Server: The Licensing Advantage
Oracle VM Server for x86 is Oracle's own hypervisor, based on the open-source Xen hypervisor. It is available free of charge. Its critical licensing advantage is its classification as an approved hard partitioning technology — when configured with hard-pinned vCPUs.
Hard-Pinned vCPU Configuration
When Oracle VM Server is configured to pin a virtual machine's vCPUs to specific physical processor cores — without allowing migration or sharing across other cores — Oracle recognises this as hard partitioning. The Oracle Database licence obligation is calculated based only on the pinned processor allocation, subject to Oracle's core factor table, not based on all host processors.
The practical result is that an enterprise can deploy Oracle Database in an Oracle VM with 8 pinned vCPUs on a 64-core physical server, and licence only those 8 vCPUs (applying the relevant core factor) — not all 64 host cores. This is the foundational cost advantage of Oracle VM over VMware for Oracle Database workloads.
Limitations of Oracle VM
Oracle VM's licensing advantages come with operational trade-offs. Hard-pinned vCPU configuration eliminates the dynamic resource flexibility that makes VMware valuable — Oracle VMs with pinned vCPUs cannot use VMware-style dynamic resource balancing. Oracle VM's management tooling (Oracle VM Manager) is mature but less feature-rich than VMware vCenter, and the ecosystem of third-party tools supporting Oracle VM is significantly smaller than the VMware ecosystem. Oracle VM performance and density characteristics are comparable to VMware for Oracle-specific workloads but the platform requires Oracle-specialised operations teams.
Real-World Cost Scenarios
The following scenarios illustrate the licensing cost differential between VMware and Oracle VM for equivalent Oracle Database deployments. All calculations use Oracle Database Enterprise Edition at a negotiated price of $15,000 per processor licence and an Intel Xeon core factor of 0.5.
Scenario A: Single Oracle DB VM on a 4-Socket VMware Host
Infrastructure: 4-socket physical server, 16 cores per socket (64 cores total), VMware vSphere
Oracle workload: 1 Oracle Database EE VM with 4 vCPUs allocated
VMware licensing obligation: 4 sockets × 16 cores × 0.5 (core factor) = 32 processor licences
Oracle VM licensing obligation: 4 hard-pinned vCPUs × 0.5 (core factor) = 2 processor licences
Annual cost difference at $15,000/processor: (32 − 2) × $15,000 = $450,000 in licence value, plus $99,000 per annum in support cost difference
Scenario B: 5-Node VMware Cluster, Multiple Oracle VMs
Infrastructure: 5 physical hosts, each 2-socket with 20 cores per socket, VMware vSphere cluster with vMotion enabled
Oracle workload: 3 Oracle Database EE VMs distributed across the cluster
VMware licensing obligation (Oracle's position): 5 hosts × 2 sockets × 20 cores × 0.5 = 100 processor licences
Oracle VM licensing obligation (equivalent workload): 3 VMs × 4 hard-pinned vCPUs each × 0.5 = 6 processor licences
Annual cost difference: 94 processor licences × $15,000 + $3,102,000 support over 5 years = over $4.5M in five-year TCO difference
The Broadcom Acquisition Impact
Broadcom's 2023 acquisition of VMware has introduced a new dimension to the Oracle-on-VMware cost analysis. Broadcom's restructuring of VMware's commercial model — moving to a subscription-based VMware Cloud Foundation bundle, eliminating perpetual licensing, and significantly increasing pricing for many VMware customers — has materially changed the total cost of VMware infrastructure for Oracle workloads.
Enterprises facing both VMware price increases under Broadcom and Oracle licensing compliance exposure for their VMware-hosted Oracle workloads are experiencing a compound cost pressure that was not present before 2023. Some enterprises we have advised have found that the combination of Broadcom VMware price increases and Oracle compliance remediation costs justifies an infrastructure re-platforming to Oracle VM, bare metal, or cloud — even accounting for migration costs and operational disruption. See our detailed guide to the Broadcom acquisition implications: VMware / Broadcom Vendor Intelligence.
Strategic Infrastructure Options for Oracle Workloads
Enterprises managing Oracle Database workloads in 2026 have four primary infrastructure options, each with distinct licensing and operational cost profiles.
Option 1: Dedicated Physical Servers
Dedicated physical servers for Oracle workloads — with no virtualisation — eliminate the partitioning policy complexity entirely. Oracle is licensed based on the physical processors in the server. For organisations with large, stable Oracle workloads that consume most of the server's capacity, dedicated physical hardware avoids virtualisation licensing risk and provides predictable costs. The trade-off is reduced infrastructure flexibility and typically higher hardware capital expenditure.
Option 2: Oracle VM Server
Oracle VM with hard-pinned vCPU configurations provides virtualisation flexibility while maintaining Oracle's approved hard partitioning status. The licensing cost advantage over VMware is substantial, as illustrated above. Oracle VM is most appropriate for organisations that need virtualisation density for Oracle workloads and are willing to operate a parallel infrastructure stack (VMware for non-Oracle, Oracle VM for Oracle).
Option 3: Oracle Cloud Infrastructure (OCI)
Oracle Cloud Infrastructure offers Oracle Database licensing on an OCPU basis, which Oracle counts as equivalent to 2 physical cores. OCI pricing for Oracle Database — either via BYOL or Oracle's cloud-specific licences — is structured to favour cloud deployment. For enterprises with Oracle ULAs that include cloud coverage, OCI deployments may be certifiable under the ULA at favourable cost. The trade-off is vendor concentration and cloud-specific dependency.
Option 4: Authorised Cloud Environments (AWS, Azure, GCP)
Oracle's authorised cloud environments — AWS, Azure, and GCP, under specific configurations — allow Oracle Database to be licensed based on OCPUs (2 physical cores each) rather than all host physical cores. This provides a middle path: enterprise cloud flexibility with Oracle-friendly licensing, at a cost premium over self-managed infrastructure. The authorised configurations are specific and must be correctly implemented to qualify — incorrect configurations default to standard Oracle licensing rules.
Related Resources
Back to the cluster pillar: The Complete Guide to Oracle Licensing & Contract Negotiation (2026).
Also in this cluster: Oracle Partitioning Rules: VMware, Hyper-V and Cloud, Oracle Audit Defence Guide, Oracle SE2 Licensing Changes.
White papers: Oracle Negotiation Playbook · Vendor intelligence: VMware / Broadcom, Oracle.
If you are running Oracle workloads on VMware and concerned about your licence position, our Vendor Audit Defence team can conduct an independent assessment before Oracle does. Contact us for a confidential review.