What is a dedicated Oracle cluster?
A dedicated Oracle cluster is a set of hosts that runs Oracle and nothing else, physically separated from the rest of the virtual estate, so that licensing is bounded by the cluster's own cores. Instead of letting Oracle virtual machines live in a shared environment alongside other workloads, the buyer carves out a defined group of servers, places Oracle there, and keeps everything else out. The boundary is the cluster itself, and that boundary is what caps the licensing requirement.
The reason this matters is the cluster wide claim. Oracle's partitioning policy does not recognise VMware as hard partitioning, so in a shared cluster Oracle can argue that every host the workload could reach is licensable. A dedicated cluster removes that argument at its root, because there is no larger pool for the claim to expand into. The licensable cores are simply the cores in the dedicated cluster, which is a number the buyer chooses and can size to its actual Oracle demand.
Why is a dedicated cluster the standard defense?
A dedicated cluster is the standard defense because it answers the cluster wide claim by removing the mobility the claim depends on, rather than arguing about it after the fact. The cluster wide claim works by treating Oracle as licensable wherever the workload could move. If Oracle is confined to a cluster it cannot leave, there is nowhere else for it to move, and the claim collapses to the cluster's own cores. This is a structural defense, built into the architecture, not a dispute the buyer has to win line by line every time.
It is also far easier to prove than the alternatives. Defending a shared cluster means demonstrating that host affinity rules genuinely pinned Oracle to a subset of hosts and that the rules held over time, which is detailed evidentiary work. A dedicated cluster reduces the question to a simpler one: is the cluster isolated, and does Oracle stay inside it. That is a cleaner story to tell an auditor and a cleaner record to keep. Because virtualization is one of the most common audit triggers, having the strongest available defense already in place is worth the design effort.
| Approach | Licensable scope | Proof burden |
|---|---|---|
| Shared cluster, no controls | Whole cluster or more | Highest exposure |
| Shared cluster, host affinity | Subset of hosts | Detailed evidence needed |
| Dedicated Oracle cluster | Cluster cores only | Simplest to prove |
| Hard partitioning | Defined core subset | Recognised by policy |
Does a dedicated cluster need supporting evidence?
Yes, a dedicated cluster still needs supporting evidence, because the defense rests on the isolation being real and provable, not merely intended. A cluster described as dedicated but connected to the wider environment through shared management, linked clusters, or a path that would let a virtual machine migrate out is not truly isolated, and Oracle will probe exactly those connections. The evidence that defends the position shows the separation: the cluster configuration, the management boundaries, and the controls that prevent Oracle from moving beyond the dedicated hosts.
That evidence works best when it is contemporaneous, captured as part of normal operations rather than assembled after a finding. Configuration records showing the cluster's membership, settings that block migration outside it, and dated proof that Oracle ran only on those hosts together establish that the isolation held throughout the audit period. A buyer who holds that record can answer a cluster wide claim immediately, showing that the architecture confined Oracle by design and that the confinement was maintained, which is far stronger than reconstructing the picture under a 30 to 45 day response window.
How do you design a dedicated cluster properly?
You design a dedicated cluster properly by isolating it at every layer that could otherwise become a path for the claim, so the separation is complete rather than nominal. The hosts run Oracle workloads only. The cluster is not joined to other clusters in a way that would extend the licensable scope. Management features that could migrate a virtual machine across boundaries are configured so they cannot move Oracle outside the dedicated hosts. Each of these decisions closes a route that an auditor would otherwise explore, and together they make the boundary defensible.
Sizing is the other half of the design. Because the dedicated cluster's cores set the licensing requirement, the cluster should be sized to Oracle's genuine demand with sensible headroom, not over provisioned with capacity Oracle does not need. Every core in the dedicated cluster is a licensable core, so excess hardware is wasted license. A well designed dedicated cluster matches its core count to the workload, which gives the buyer a predictable, contained licensing position rather than the open ended exposure of a shared environment.
How does a dedicated cluster hold up in an audit?
A dedicated cluster holds up in an audit because it gives the buyer a simple, evidenced answer to the question an auditor is trying to expand: where can Oracle run. When the collection scripts report usage, the buyer can show that Oracle is confined to a defined cluster, that the cluster is isolated, and that the licensable cores are its own. There is no larger pool to argue over, which removes the single largest source of inflation in virtualized findings before the dispute even starts.
The architecture also pairs with the contract argument. Oracle's cluster wide claims rest on the partitioning policy, and the policy document is not the contract, so even a shared cluster can be defended on the basis that policy does not override the signed agreement. A dedicated cluster strengthens that position by making the factual footprint indisputable: regardless of how the policy is read, Oracle demonstrably ran only on the dedicated hosts. Oracle's preliminary findings arrive inflated at list price, and an independent line by line review of findings typically cuts claims by 60 to 80 percent, but the dedicated cluster aims higher, removing the cluster wide claim at the design stage so it never becomes a finding to reduce.
The next step
This article is part of our Virtualization and VMware cluster. Read the pillar, the Oracle virtualization licensing guide, for the full picture, and these related reads: the Oracle virtualization licensing guide blog, and host affinity rules and evidence.