Oracle's partitioning policy sits behind nearly every large virtualization finding, and it is widely misunderstood as a rule the customer is bound to follow. It is not. It is a policy document that states Oracle's preferred interpretation of how virtualized estates should be licensed, and its central claim, that software virtualization does not reduce the licensable footprint, is the engine of the cluster wide finding. Understanding what the policy actually is, and what it is not, is the foundation of every virtualization defense.
Does Oracle's partitioning policy recognise VMware?
Oracle's partitioning policy does not recognise VMware, Hyper V or KVM as a way to limit licensing, classifying them as soft partitioning rather than the hard partitioning it approves. Under this reading, running an Oracle database in a virtual machine does not mean you license only that virtual machine. The policy treats the whole physical host as licensable, and in clustered environments where virtual machines can move between hosts, it extends the claim to every server in the cluster the workload could theoretically run on. That extension is how a single small database becomes a finding spanning dozens of processors.
This is the most aggressive position in the policy and the one that produces the largest opening numbers. A modest Oracle footprint inside a large VMware cluster, priced cluster wide at list, can generate an exposure out of all proportion to the actual deployment. The number is real as an opening position. Whether it survives contact with the contract is another matter entirely.
What is the difference between hard and soft partitioning?
The difference is that hard partitioning physically segments a server in a way Oracle approves, so only the carved out capacity is licensable, while soft partitioning is software based and, under Oracle's policy, does not reduce the footprint at all. The policy names specific approved hard partitioning technologies, and it places mainstream hypervisors firmly in the soft category. The line is drawn by Oracle, in the policy, according to Oracle's own technical and commercial judgement about which mechanisms it will accept as a real boundary.
For a buyer, the practical consequence is that the partitioning method chosen for technical reasons carries a licensing meaning under the policy that has nothing to do with how the technology actually behaves. VMware confines a workload as effectively as many approved methods. The policy nonetheless treats it as no boundary at all. That gap between technical reality and policy classification is precisely where the argument gets had, and it is had against the policy, not the contract.
A database runs in one virtual machine on a six host VMware cluster, each host carrying two sixteen core processors. The opening finding applies the partitioning policy cluster wide, licensing all twelve processors across the cluster at list. The buyer's signed agreement, however, contains no reference to the partitioning policy and defines the licensable unit by the processors on which the program is installed and running. The argument shifts from the policy's cluster wide reach to the contract's narrower definition, and the defensible footprint collapses from twelve processors to the small number the database actually used.
Is the partitioning policy part of the contract?
The partitioning policy is not part of the contract; it is a non contractual document that Oracle publishes and updates at its own discretion, and contract language beats policy whenever the two diverge. This single fact reframes the entire conversation. A finding that rests on the partitioning policy rests on a document you very likely never signed and never agreed to be bound by. Your obligations are defined by the Oracle Master Agreement and the ordering documents, and those signed terms govern when there is a conflict. Many cluster wide claims rest on policy papers that are weaker than the signed agreement they are meant to enforce.
So the defense begins by separating the two sources. Read the contract for how it actually defines the licensable unit, where the program must be installed and running for a licence to be required, and whether the partitioning policy is incorporated by reference at all, which it usually is not. Then hold the finding to the contract rather than the policy. A cluster wide number assembled from a non contractual document is an opening position, and an independent line by line review of Oracle findings typically cuts a claim 60 to 80 percent, with virtualization among the strongest categories precisely because so much of the claim rests on policy rather than on signed terms.
The policy is the opening move; the defense is contractual and evidential. See disputing cluster wide virtualization claims and how scripts overcount in virtualized estates for the next steps, and the full method in the Oracle virtualization licensing guide.