Oracle's partitioning policy decides how many processors you license on virtualized hardware. It is a policy document, not your contract, and that distinction matters.
Oracle's partitioning policy sets out which virtualization technologies Oracle treats as limiting your license count and which it does not. It is the rule that turns a small server into a large license claim.
The policy is a document Oracle publishes, not a clause in your license agreement. Understanding that gap is the whole game when Oracle counts your virtual estate.
The Oracle partitioning policy states which technologies Oracle accepts as hard partitioning, which bind your license to a subset of cores. Everything else is soft partitioning and is licensed as if Oracle could run on the entire physical host.
Oracle publishes this in the Oracle Partitioning Policy document. It is guidance Oracle applies, and it sits outside the Oracle Master Agreement you actually signed.
The policy is not part of your signed agreement unless it is referenced into it. That gap is why buyers can sometimes contest a soft partitioning claim, though architecture is a stronger position than argument.
Hard partitioning physically or firmly limits which cores can run Oracle. Soft partitioning uses software that Oracle says could be reconfigured, so Oracle declines to recognize it as a limit.
Hard versus soft partitioning
| Type | Examples | Oracle treatment |
|---|---|---|
| Hard | Approved capping technologies | Licenses bound to cores |
| Soft | Common hypervisor live migration | Whole host licensed |
| Cloud | Authorized OCPU shapes | Per OCPU counting |
The detailed database licensing rules sit in the Oracle Database Licensing Information documentation. The processor count always flows from the partitioning treatment first.
Oracle argues that software limits can be changed, so it cannot rely on them. The practical effect is that a single Oracle node on a large host can license the whole host.
VMware is the flashpoint because Oracle treats it as soft partitioning and may claim every host a virtual machine could migrate to. The license boundary becomes the cluster, not the server.
Oracle has argued that the boundary is every host within reach of live migration, including across linked clusters. That scope can multiply the count several times over.
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
You defend a partitioning claim with architecture and evidence, not debate. The strongest position is a contained estate Oracle cannot credibly extend.
Configuration that proves Oracle can only run on the hosts you licensed wins, and it is what Oracle License Management Services ultimately measures. Logs, cluster settings, and migration boundaries beat any conversation about policy intent.
The standard advice is to fight Oracle's soft partitioning stance by arguing that the policy is not contractually binding. We disagree. In most virtualization engagements we ran, that argument alone did not lower the claim, because Oracle holds the audit position and the burden of proof falls on the buyer. The far stronger buyer side move is architectural: isolate Oracle onto a dedicated cluster, cut the live migration paths, and make the licensed boundary physically provable. Win the count with configuration, then use the policy gap as a negotiation lever, not as your whole defense. A legal argument with no architecture behind it rarely moves an Oracle reviewer.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The Oracle partitioning policy defines which virtualization technologies Oracle accepts as limiting your license count. Approved hard partitioning binds licenses to specific cores, while soft partitioning is licensed as the whole host.
The policy is a document Oracle publishes and applies, not a clause in your signed agreement unless it is referenced into the contract. That gap is why some soft partitioning claims can be contested.
Hard partitioning firmly limits which cores can run Oracle, so licenses bind to those cores. Soft partitioning uses software Oracle says could be changed, so Oracle counts the entire physical host.
Oracle treats VMware as soft partitioning and may claim every host a virtual machine could reach through live migration, which can extend the license boundary to a whole cluster.
Isolate Oracle workloads onto a dedicated, separately licensed cluster, disable migration paths into non Oracle hosts, and document the architecture so the boundary is provable.
Arguing the policy is not binding rarely lowers the claim on its own. A contained architecture that proves where Oracle can run is a far stronger buyer position.
Authorized cloud shapes use per OCPU counting rather than the on premises partitioning policy, which is one reason isolating Oracle to cloud or a dedicated cluster can simplify exposure.
In our engagements, soft partitioned estates faced claims a median 3.5 times the cores actually running Oracle, driven by Oracle extending the boundary across the migration cluster.
A buyer side reference for the Oracle estate. ULA exit moves, Java audit defense posture, certification framework, and the levers that move an Oracle renewal.
Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying Oracle Database, Java, and applications spend. No Oracle kickback. No conflict on the table.
Oracle ULA Decision Framework
Open the framework in your browser. Corporate email only.
Get the Framework →Win the count with configuration, then use the policy gap as a lever.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Oracle Database benchmarks, ULA exit patterns, Java audit posture, and OCI commitment math from every Oracle engagement we run on the buyer side.
