A VMware soft partitioning defence cut an $18M Database audit claim to $4.2M.
A public sector body was audited on the basis that its entire VMware estate required Oracle Database licensing, regardless of where the databases actually ran.
A public sector body was audited on the basis that its entire VMware estate required Oracle Database licensing, regardless of where the databases actually ran.
The client, a large public sector body, ran Oracle Database Enterprise Edition on a virtualised estate built on VMware. Oracle opened an audit and asserted that, because VMware is treated as soft partitioning under Oracle's partitioning policy, every physical host across which a virtual machine could potentially run had to be fully licensed for Oracle Database, regardless of where the databases actually ran. Applied across the body's VMware clusters, this produced an opening claim of $18.0M.
The soft partitioning position is the single most contested issue in Oracle Database licensing. Oracle's policy document does not recognise VMware as an approved means of partitioning, and on that basis Oracle routinely argues that licensing must cover every processor in every host that a virtual machine could be live migrated to. In large VMware estates with broad clusters and vMotion enabled across many hosts, this interpretation can multiply the licensing requirement many times over the hosts where Oracle actually runs.
The crucial point is that the partitioning policy is a policy document, not a contract term. The body's contract licensed Oracle Database on its defined metrics and did not incorporate the partitioning policy as a binding obligation. The gap between what the policy asserts and what the contract actually requires is precisely where a soft partitioning claim is won or lost. The body had been managing its estate without a defined boundary between Oracle and non Oracle hosts, which is what allowed Oracle to argue the broadest possible cluster scope.
The body needed to establish where Oracle databases genuinely ran, what the contract actually obliged it to license, and how to constrain the estate so the defensible position could be sustained going forward.
The Containment phase was critical here because the scope of data the body provided would define the scope of the claim. We controlled the discovery so that the measurement reflected where Oracle actually ran rather than the full theoretical reach of every cluster, and we ensured no configuration data left the perimeter without buyer side review.
The Measure phase established the genuine Oracle footprint. We documented every virtual machine running Oracle Database, the hosts those machines actually ran on, and the cluster topology including which hosts were in scope for live migration. We then mapped this against the contract, because the licensing obligation flows from the contract metrics, not from the partitioning policy. The objective was to define the smallest defensible licensable boundary supported by both the deployment reality and the contractual language.
The legal and technical analysis ran together. We assessed the contract for any clause that incorporated the partitioning policy as binding, and found none, which meant Oracle's full cluster argument rested on a policy the contract did not adopt. We documented the actual placement of Oracle workloads and built the position that licensing should follow the hosts where Oracle ran, constrained by the cluster boundaries the body could evidence and commit to.
In the Negotiate phase we argued the distinction between policy and contract directly. The full cluster claim assumed an obligation the contract did not contain. By presenting the documented Oracle footprint, the absence of a contractual partitioning policy incorporation, and a committed cluster segregation going forward, we reduced the licensable scope from the entire VMware estate to the defined hosts where Oracle genuinely ran.
The Convert phase made the defensible position permanent. The body committed to a segregated cluster design in which Oracle workloads run on dedicated, clearly bounded hosts isolated from the wider VMware estate, with vMotion constrained to that boundary. The settlement licensed that bounded footprint, and the contract documented the segregation so the soft partitioning argument cannot be re run against the same estate at the next audit.
The partitioning policy is a policy document, not a contract term. The gap between what the policy asserts and what the contract requires is where a soft partitioning claim is won or lost.
The $18.0M full cluster claim settled at $4.2M, a reduction of 77 percent, licensing the bounded Oracle footprint rather than the entire VMware estate. The table shows how the scope was constrained.
| Exposure category | Oracle claim | Settled |
|---|---|---|
| Full VMware estate (as claimed) | $18.0M | n/a |
| Hosts with no Oracle workload | -$10.6M | excluded |
| Unconstrained migration scope | -$3.2M | constrained |
| Bounded Oracle cluster footprint | $4.2M | $4.2M |
The settlement licensed a defined, bounded Oracle footprint rather than the entire VMware estate. The body committed to a segregated cluster design in which Oracle Database workloads run on dedicated hosts with live migration constrained to that boundary, and the contract documented that segregation so the position is evidenced and sustainable.
Because the soft partitioning argument rested on a policy the contract did not incorporate, documenting the bounded footprint and the cluster segregation removes the basis for re running the full cluster claim. The body now holds a defensible virtualisation position and a clear design rule for placing Oracle workloads going forward.
For the buyer side perspective on this product line, our Oracle Database licensing team and our Oracle audit defence practice work the same playbook on every engagement. Compare outcomes across the full case study library.
If an Oracle audit prices your entire VMware estate on the soft partitioning argument, the contract often says far less than the policy claims. We define the defensible boundary before you respond.
Request a Consultation