Why is Oracle virtualization licensing so expensive?
Oracle virtualization licensing is expensive because Oracle counts capacity you could use, not capacity you do use. When an Oracle Database or option runs inside a virtual machine, Oracle argues that the software could move to any host in the cluster, so every processor in that cluster must be licensed. On a large VMware estate that turns a handful of database hosts into hundreds of licensable cores, and the preliminary finding lands at list price.
The argument is frequently overstated. It rests on Oracle policy papers, and the policy document is not the contract. Where your signed agreement does not support a cluster wide reading, the defensible number is far smaller. Our job is to read the contract first and the policy second.
A cluster wide VMware claim is an opening position. Test it against your signed agreement and the host topology you can actually demonstrate, and most of the finding falls away.
Does Oracle recognise VMware as hard partitioning?
No. Oracle partitioning policy recognises only a short list of technologies as hard partitioning, and VMware, Hyper V and KVM are not on it. Oracle treats them as soft partitioning, which is the basis for the cluster wide claim. That does not make the claim contractual. The defensible position depends on your architecture, the way clusters and storage are segmented, the version of VMware in use, and what your agreement actually says about counting processors.
We build the technical record that supports the smallest defensible footprint: cluster boundaries, host affinity rules, and evidence of where the software has and has not run. Combined with a contract that often says less than Oracle assumes, that record is what disputes a multi million dollar finding down to a fraction. The mechanics are set out in why VMware is not hard partitioning to Oracle and across Hyper V and KVM under Oracle policy.
| Oracle position | Buyer side challenge |
|---|---|
| License every host in the cluster | Demonstrate where the software actually runs |
| Apply soft partitioning policy | Test the policy against the signed contract |
| Count at list price | Recompute with the correct core factor |
| Treat connected clusters as one | Document cluster and storage segmentation |
How is Oracle licensed on AWS, Azure and OCI?
Oracle counts vCPUs under its cloud computing policy on authorised clouds, and the rule differs from on premises cores. On AWS and Azure the policy converts vCPUs to a license requirement, and the conversion is not the same as the core factor table you use in your data center. On OCI the counting follows Oracle own rules, and Support Rewards can offset support spend through OCI consumption, which changes the commercial picture rather than the compliance one.
The mistake we see most often is applying on premises maths to a cloud deployment, or assuming a bring your own license move is automatically compliant. Each cloud has its own counting rule, and each has to be checked against the policy in force and your contract. See counting vCPUs on AWS and Azure for the detail.
Whether a specific cloud deployment is compliant is contract dependent. It turns on your cloud and territory terms and the policy version that applies, so we read it against your signed agreement rather than assume it from policy.
What does this service include?
We take the whole virtualization and cloud position end to end. We map the estate independently, document the smallest defensible footprint, recompute every count with the correct core factor, test Oracle policy against your signed contract, and carry the dispute through to a settled number. Where a cloud move is planned, we model the license position before you migrate so the move does not create exposure.
- Independent deployment and cluster mapping, separate from Oracle scripts
- Contract review against the partitioning and cloud policy in force
- Line by line recomputation of processor and vCPU counts
- Dispute strategy and settlement support through to a final number
- Pre migration modelling for AWS, Azure and OCI
For the wider audit picture this connects to our audit defense guide, and for standing position work to the license compliance review.
How do you price this service?
We work on two pricing models only. A Fixed Fee, scoped and agreed up front, where you know the cost before we begin. Or Gainshare, a share of verified savings or avoided exposure, with zero retainer and no risk to you. Our guarantee is simple: we reduce your Oracle exposure or we reimburse our service fee. We never publish a price because the right model depends on your estate and your situation.
Send us the outline of your VMware or cloud estate and we will come back with a scoped approach. Request a quote or read the virtualization licensing guide first.