What is the Oracle cluster wide licensing claim?
The Oracle cluster wide licensing claim is the argument that on a VMware estate you must license every physical host on which an Oracle database could possibly run, rather than only the hosts where it actually runs. It flows from Oracle's partitioning policy, which does not recognise VMware, Hyper V, or KVM as hard partitioning, meaning Oracle treats the soft partitioning these provide as no boundary at all. From there the claim expands: if a virtual machine can migrate across a cluster, Oracle asserts every host in that cluster is a place the database could run, and in newer VMware architectures the claim can reach across linked clusters too. The result is a finding sized to the whole virtual estate, not the workload. The full treatment is in the Oracle Virtualization Licensing Guide.
Why is the cluster wide claim weak?
The cluster wide claim is weak because it rests on a policy document rather than the signed Oracle Master Agreement, and where the two differ the contract governs. Oracle's partitioning policy is a paper Oracle publishes and updates, not a term the customer negotiated and signed, and it is frequently more restrictive than the agreement it purports to interpret. The agreement typically licenses the database as a program installed and running, and it does not usually contain the words that would oblige a customer to license every host in a vMotion boundary. So when an auditor presents a cluster wide finding, the foundation is the policy, and the policy is contestable precisely because it is not the contract. This is the single most important fact in any virtualization dispute: contract language beats policy.
When a cluster wide finding lands, go straight to the signed agreement. Read the licence grant and the definitions, then test the policy claim against them. The policy is an opening position, and the contract is the rule that actually binds.
How do you respond to a cluster wide finding?
You respond to a cluster wide finding by reading the signed agreement against the policy the auditor cites, establishing exactly where the database actually ran, and declining any claim the contract does not support. Start with the agreement, because it is the binding instrument and it sets the ceiling on what Oracle can require. Then assemble the evidence of real deployment: which hosts the virtual machines actually ran on, what the migration boundaries genuinely were, and where the data shows the database never went. A cluster wide claim asserts possibility, and possibility is not deployment. Where the contract is silent on host wide licensing and the policy supplies the only basis for the expansion, the buyer position is that the policy cannot add an obligation the agreement never created. See the policy document versus your contract and disputing cluster wide virtualization claims.
| Oracle policy claim | Contract reality | Buyer position |
|---|---|---|
| VMware is not hard partitioning | Agreement defines the program | Read the grant, not the policy |
| License every host in the cluster | Database ran on specific hosts | Possibility is not deployment |
| Claim spans linked clusters | Migration boundary is provable | Show where it actually ran |
| Policy sets the requirement | Contract governs first | Contract language beats policy |
What is the next step?
The next step is to retrieve your signed Oracle agreement, read its grant and definitions against the partitioning policy, and build the deployment evidence before you respond to any cluster wide finding. The claim looks large at list price, but its foundation is a policy you never signed, and an independent line by line review typically cuts virtualization findings substantially once the contract and the real deployment are on the table. Download the virtualization guide for the contract versus policy method and the evidence checklist, and bring us your finding when you want the recount done.
Download the VMware Licensing Survival Guide for the contract versus policy method and the deployment evidence checklist. Get it from the white paper library, or read the full Oracle Virtualization Licensing Guide.