Oracle Database deployed on VMware infrastructure is the single most contested licensing scenario in the Oracle product line. Oracle treats VMware as a soft partitioning technology under the Oracle partitioning policy. The policy requires the buyer to licence every physical core in every server that is part of the VMware cluster regardless of whether the Oracle workload is running on that server. The policy can extend the licence requirement across the entire VMware estate if vMotion is enabled across multiple clusters. The Oracle partitioning policy is not a contract term in the standard customer agreement. It is published guidance that Oracle applies during audits. The legal status of the policy is contested. The operational impact on buyers is substantial. This article describes the policy, the contract position, the buyer defence pattern, and the operational options.
The partitioning policy as published.
The Oracle partitioning policy is published on the Oracle pricing site as a document titled Oracle Partitioning Policy. The policy distinguishes between hard partitioning and soft partitioning technologies. Hard partitioning technologies are listed in the policy and include certain mainframe partitioning options, certain Solaris and IBM hardware options, and Oracle VM Server in specific configurations. Hard partitioning allows the buyer to licence only the partition that runs the Oracle workload.
Soft partitioning includes everything else. The policy lists VMware ESX as a soft partitioning technology by name. The policy states that soft partitioning is not permitted as a means to determine or to limit the number of software licences required. The implication is that the buyer must licence every physical core in every server that is part of the soft partitioned environment. The implication has been applied by Oracle during audits to require licensing of the entire VMware cluster.
The contract position.
The partitioning policy is not referenced in the standard Oracle customer agreement. The customer agreement defines the processor metric and the Named User Plus metric. The agreement does not specify that the metric must be applied at the cluster level or at the estate level in virtualised environments. The partitioning policy is published guidance that supplements the contract. The legal status of the supplementary guidance is contested.
The buyer contract position is that the metric is defined in the contract and that any expansion of the metric requires the agreement of the buyer. The policy is the Oracle interpretation. The contract is the binding document. A buyer that has not signed an amendment incorporating the partitioning policy into the contract has a contract argument that the policy is not binding. The argument has not been tested in the courts. It has been used as a negotiation position in audit settlements.
The vMotion expansion.
The Oracle audit position on VMware deployments has expanded over time. The early position required licensing of every physical core in the cluster that runs the Oracle workload. The current position can require licensing of every physical core in every server that is reachable by the Oracle workload through vMotion. If vMotion is enabled across multiple clusters the licence requirement can extend across the entire VMware estate.
The vMotion expansion produces the largest audit findings. A buyer with ten clusters and one cluster running Oracle can be required to licence all ten clusters under the expanded position. The expansion is contested. The contract argument and the technical argument both support the buyer position that the licence requirement is limited to the cluster running the Oracle workload. The audit settlement typically lands somewhere between the two positions.
Technical isolation patterns.
The buyer operational response to the partitioning policy is technical isolation. Buyers can build dedicated Oracle clusters that are physically and logically isolated from the rest of the VMware estate. The isolated cluster has no vMotion connectivity to other clusters and no shared storage with other clusters. The isolated cluster also has no shared DRS or HA configuration with other clusters.
The isolation reduces the audit exposure to the boundaries of the isolated cluster. The isolation requires investment in infrastructure and in operational discipline. The isolation also limits the operational flexibility that VMware otherwise provides. Buyers should consider whether the cost of isolation is less than the cost of the audit exposure under the expanded position.
Storage and the SAN question.
Shared storage between clusters introduces a second expansion vector. The Oracle audit position can argue that a cluster that shares storage with another cluster is functionally connected to the second cluster. The audit position can therefore extend the licence requirement to both clusters even without vMotion connectivity. The argument is more aggressive than the vMotion argument and has been contested.
The buyer technical response is to isolate the storage as well as the compute. Dedicated storage arrays or dedicated LUNs for the Oracle cluster reduce the audit exposure. The technical response is operationally expensive but reduces the legal exposure under the audit position.
The negotiation position.
The negotiation position on the VMware question depends on the audit posture. A buyer that has not yet been audited can negotiate a side letter or an amendment that defines the cluster boundary for the licence requirement. The side letter clarifies the contract and removes the ambiguity. The negotiation should occur during the next contract event such as a renewal or a new licence purchase.
A buyer that is in audit should negotiate the settlement on the contract position rather than on the published policy. The settlement should record the cluster boundary that applies for the period of the settlement. The settlement should also include a defined process for resolving future disagreements without escalation to formal audit. See the processor licence audit issues note for the broader audit context.
Engaging an independent advisor.
The VMware position benefits from external technical, contract, and negotiation expertise. An independent advisor brings the experience of running multiple VMware defences and can build the technical isolation plan, the contract position, and the negotiation strategy on a coordinated track.
For the wider cluster see Licensing Compliance. For the service see Audit Defense. For the deal structure see the Database licensing page. For the Oracle product see the Oracle Database product page. For the full research read the Oracle Negotiation Playbook white paper.
The documentation position.
The buyer documentation position is the foundation of any VMware defence. The documentation should include the VMware infrastructure inventory, the cluster boundaries, the vMotion configuration, the storage configuration, and the Oracle workload deployment map. Each component should be documented at the current state and should be supported by historical records that demonstrate the configuration through the audit period.
The documentation should be assembled before any Oracle conversation rather than in response to an audit request. The documentation produced in response to an audit request is less credible than documentation produced as part of the standard operational record. Buyers should treat the VMware documentation as a standing requirement rather than as an audit response.
A worked example.
A European energy buyer received a VMware focused Oracle audit in 2023. The audit position required licensing of all twelve VMware clusters in the estate on the basis that vMotion was theoretically possible between all clusters. The Oracle audit proposal was approximately eighteen hundred processor licences against a deployed Oracle workload that required approximately two hundred processor licences if licensed at the workload level.
The buyer engaged an independent advisor. The advisor reviewed the VMware configuration and identified that vMotion was technically enabled across the estate but was operationally restricted by storage boundaries and by network segmentation. The advisor also reviewed the contract and identified that the buyer had never signed an amendment incorporating the partitioning policy. The contract position supported a licence count limited to the clusters that ran the Oracle workload.
The settlement recognised four hundred and twenty processor licences for the clusters that ran or could readily run the Oracle workload. The settlement was approximately two thousand processor licences below the original audit proposal. The buyer subsequently implemented full cluster isolation to remove the residual exposure and to set a defensible position for future audits.
The migration option.
The strategic alternative to the VMware partitioning dispute is migration of the Oracle workloads off VMware. The migration options include Oracle Linux KVM which appears on the hard partitioning list under specific configurations, Oracle Cloud Infrastructure which carries its own counting model, and dedicated bare metal infrastructure which removes the virtualisation question entirely. Each option has technical, operational, and commercial implications that should be assessed against the cost of the partitioning exposure.
The migration option is most useful when the buyer is approaching a refresh of the underlying infrastructure. A refresh that would have replaced the VMware estate anyway is a natural moment to remove the Oracle partitioning exposure. A migration motivated only by the partitioning policy is harder to justify commercially because the migration costs are real and the partitioning exposure is contested.
Buyers should also consider that the migration option is a credible alternative in the negotiation conversation even when the buyer does not intend to execute the migration. A credible alternative changes the Oracle commercial position. See the database to AWS RDS migration note for the related alternative pattern.