1. What Is the Oracle Partitioning Policy Document?
The Oracle Partitioning Policy is a publicly available document that Oracle uses to define which virtualisation technologies are approved for sub-capacity licensing of Oracle software. It establishes the rules under which an enterprise can licence only a portion of a server — rather than the entire physical machine — when running Oracle products in virtualised environments.
The document is essential reading for anyone responsible for Oracle licensing in environments that use VMware, Hyper-V, Nutanix AHV, Docker, Kubernetes, or any other virtualisation technology. It creates a sharp divide between two categories of technology:
Hard partitioning — Oracle-approved methods that physically limit which cores Oracle software can use. If you use hard partitioning, Oracle permits sub-capacity licensing: you licence only the partitioned resources, not the entire server.
Soft partitioning — Every other virtualisation technology that Oracle has not explicitly approved. Soft partitioning does not reduce your licence obligation. You must licence all physical cores on every server or cluster where Oracle software could potentially run.
This distinction has enormous financial consequences. The difference between hard and soft partitioning for the same Oracle workload can range from hundreds of thousands to millions of dollars. For a detailed financial analysis with real numbers, see our guide on Oracle Partitioning Policy Cost Impact: Real-World Scenarios.
The Oracle Partitioning Policy is Oracle's single most powerful licensing enforcement tool. It is the mechanism Oracle uses to demand full-capacity licensing for VMware clusters, Hyper-V environments, and Nutanix deployments. Understanding this document — and its legal limitations — is the foundation of any Oracle virtualisation licensing strategy.
2. Hard Partitioning: Oracle-Approved Sub-Capacity Licensing
Hard partitioning refers to Oracle-approved technologies that physically limit the number of processors or cores available to an Oracle instance. When correctly configured, hard partitioning allows you to licence only the resources allocated to Oracle — not the full server. This is what Oracle calls sub-capacity licensing.
The critical word is "approved." Oracle maintains a specific list of technologies it considers hard partitioning. If a technology is not on this list, it is automatically classified as soft partitioning — regardless of how effective it is at isolating resources. For the complete implementation guide, see Implementing Oracle-Approved Hard Partitioning.
Complete List of Oracle-Approved Hard Partitioning Technologies
| Technology | Platform | Key Requirement | Sub-Capacity Allowed? |
|---|---|---|---|
| Oracle VM (OVM) with CPU Pinning | x86 (Oracle Linux KVM) | VMs must be pinned to specific physical CPUs; pinning must remain fixed | ✅ Yes |
| Oracle Linux KVM with CPU Pinning | x86 (Oracle Linux) | CPU affinity set and capped; no dynamic reallocation | ✅ Yes |
| IBM LPAR (Logical Partitions) | IBM Power Systems (AIX) | Must be capped partitions; DLPAR with AIX 5.2+ | ✅ Yes (capped only) |
| IBM Micro-Partitions | IBM Power Systems | Must be capped; uncapped partitions = soft partitioning | ✅ Yes (capped only) |
| Solaris Zones / Containers | Oracle Solaris | Must be capped Zones with fixed CPU allocation | ✅ Yes (capped only) |
| Physical Domains (PDomains) | Oracle SPARC servers | Also called Dynamic Domains; hardware-level isolation | ✅ Yes |
| HP vPar | HP-UX (Integrity) | Must be capped partitions | ✅ Yes (capped only) |
| HP nPar | HP-UX (Integrity/Superdome) | Hardware-level isolation | ✅ Yes |
| HP Integrity Virtual Machine (IVM) | HP-UX Integrity | Must be capped | ✅ Yes (capped only) |
| Secure Resource Partitions | Various | Must be capped | ✅ Yes (capped only) |
| Fujitsu PPAR | Fujitsu SPARC | Must be capped | ✅ Yes (capped only) |
For every technology marked "capped only," the partition must have a hard maximum on CPU allocation that cannot be exceeded — even temporarily. An IBM LPAR configured as "uncapped" (where it can borrow idle CPU from other partitions) does not qualify as hard partitioning. Oracle will require you to licence the full physical server. The configuration must be verifiably capped at all times.
🔧 Need help implementing hard partitioning to reduce Oracle licence costs?
Oracle License Management →3. Soft Partitioning: Why Oracle Demands Full-Capacity Licensing
Soft partitioning is Oracle's term for any virtualisation technology not on the approved hard partitioning list. It includes the most widely used hypervisors and container platforms in enterprise IT. If you use soft partitioning, Oracle's position is that you must licence all physical cores on all hosts where Oracle software could potentially run — even if Oracle only uses a fraction of one host.
Technologies Oracle Classifies as Soft Partitioning
| Technology | Oracle's Classification | Licensing Consequence |
|---|---|---|
| VMware vSphere / ESXi | Soft partitioning | Licence all cores on all hosts in the cluster |
| Microsoft Hyper-V | Soft partitioning | Licence all cores on all hosts in the cluster |
| Nutanix AHV | Soft partitioning (by omission) | Licence all cores on all nodes in the cluster |
| Citrix XenServer | Soft partitioning | Licence all cores on all hosts |
| KVM (non-Oracle Linux) | Soft partitioning | Licence all cores on the host |
| Docker / Containers | Soft partitioning | Licence all cores on all hosts where container could run |
| Kubernetes | Soft partitioning | Licence all cores on all nodes in the K8s cluster |
| VM pinning / affinity rules | Not recognised as a licensing control | Oracle ignores these — still demands full capacity |
Oracle's rationale is that soft partitioning technologies use software-based controls that can be changed at any time. A VM pinned to one host today can be migrated to another host tomorrow. CPU limits set in a hypervisor can be raised with a few clicks. Oracle's argument: since these controls are not physically fixed, the Oracle software could use any resource in the environment at any time — and therefore all resources must be licensed.
For the complete guide to Oracle licensing implications on each hypervisor platform, see our articles on Oracle licensing on VMware, Oracle licensing on Hyper-V, and Oracle licensing on Nutanix.
🛡️ Running Oracle on VMware, Hyper-V, or Nutanix?
Oracle's soft partitioning rule could mean you owe millions more in licences than you think. Our former Oracle auditors can assess your actual exposure and design an architecture that dramatically reduces it.
4. The Non-Contractual Nature of the Partitioning Policy
This is the single most important legal fact about Oracle's Partitioning Policy: it is not a contract. It is not part of any contract. And Oracle says so explicitly.
At the bottom of the Oracle Partitioning Policy document, Oracle includes this disclaimer:
The implications are significant:
- The Partitioning Policy is advisory, not binding. It represents Oracle's interpretation of how licensing should work in virtualised environments — but it has no legal force unless your signed contract explicitly incorporates it by reference. In the vast majority of Oracle agreements, it does not.
- Your contract takes precedence. The Oracle Master Agreement (OMA), your Order Documents, and Schedule P define your licensing rights. If there is a conflict between what the Partitioning Policy says and what your contract says, the contract wins. Always.
- Oracle can change the policy at any time. Because it's not contractual, Oracle reserves the right to modify the Partitioning Policy without notice. Technologies that are approved today could theoretically be removed tomorrow. This makes it unreliable as a long-term licensing planning tool.
- Oracle LMS/GLAS routinely uses the policy as if it were binding. Despite its non-contractual status, Oracle's audit teams present the Partitioning Policy as the definitive authority on virtualisation licensing. Many enterprises accept this without questioning it — and pay millions in unnecessary licence true-ups as a result.
For a detailed legal analysis of how to leverage this distinction, see Oracle Partitioning Policy vs Contract Terms: How to Push Back.
In our experience defending 200+ Oracle audits, the Partitioning Policy is the single most commonly misunderstood document in Oracle licensing. Oracle's audit teams present it as law. It is not. It is an internal policy that Oracle uses to justify its preferred commercial outcome. Your contract — not Oracle's policy — defines your licence obligations. Every audit defence strategy should start with this distinction.
5. Oracle's Contractual Licence Definition: What Your Agreement Actually Says
During an audit, Oracle's LMS/GLAS team references the Oracle Master Agreement (OMA) and your Order Documents (including Schedule P) to determine your licensing position. Here is what these documents actually say about processor licensing — and critically, what they don't say.
What the OMA Grants You
The OMA grants you a non-exclusive, non-assignable, royalty-free, and perpetual right to use Oracle software for internal business purposes. The key licensing definition is for "Processor": Oracle defines a Processor as all processors where the Oracle software is installed and/or running.
What the OMA Does NOT Say
The OMA's definition of "Processor" does not reference the Partitioning Policy document. It does not say "all processors where Oracle software could potentially run." It does not mention VMware, Hyper-V, Nutanix, or any other virtualisation platform. It defines the licensing obligation as processors where Oracle is installed and/or running — a narrower definition than what Oracle's audit team typically claims.
This creates a defensible position: if Oracle software is installed and running on a VM that resides on Host A, and there is no Oracle software on Hosts B, C, or D in the same cluster, a strict reading of the OMA suggests you only need to licence Host A. Oracle will argue otherwise (citing the Partitioning Policy and the theoretical possibility of VM migration), but the contract language supports the narrower interpretation.
Challenging Oracle's interpretation of the Partitioning Policy is legally defensible but not without risk. Oracle may escalate audit negotiations, threaten legal action, or withhold cooperation on other commercial matters. This strategy works best with strong documentation, independent legal counsel experienced in Oracle disputes, and an advisory firm that has successfully defended similar positions. It is not recommended to attempt this without expert support.
⚖️ Need help interpreting your Oracle contract's virtualisation clauses?
Oracle Contract Negotiation →6. How to Challenge Oracle's Partitioning Position in an Audit
When Oracle's audit team (LMS/GLAS) presents its findings based on the Partitioning Policy, you have options. Here are the strategies enterprises use to challenge Oracle's position — ranked by effectiveness and risk. For the complete audit process and defence framework, see our Oracle Licence Audit Strategic Guide.
- Establish that the Partitioning Policy is not part of your contract. Request that Oracle's audit team identify the specific contractual clause requiring you to licence all physical cores in a cluster. In most cases, they cannot — because the OMA doesn't say that. The Partitioning Policy is not referenced in the OMA or Order Documents. This is the strongest legal foundation for any pushback.
- Document that Oracle is only installed/running on specific hosts. Maintain detailed records showing exactly where Oracle software is installed: which VMs, which hosts, which clusters. If you can prove Oracle is only on Host A, the OMA's definition of "Processor" supports licensing only Host A. Use VM placement logs, migration history (showing no movement to other hosts), and infrastructure diagrams.
- Demonstrate operational controls that prevent Oracle from running on unlicensed hosts. While Oracle doesn't officially accept VM affinity rules as a licensing control, demonstrating them strengthens your negotiating position. Show that live migration is disabled for Oracle VMs, that affinity rules pin Oracle to specific hosts, and that operational procedures prevent accidental migration.
- Propose a dedicated Oracle cluster as a compromise. If full pushback is too aggressive, offer to migrate Oracle to a dedicated, smaller cluster and licence that cluster. This gives Oracle the full-capacity licensing it wants — but on a dramatically smaller footprint. This is the most common negotiated outcome.
- Negotiate contractual clarity for future periods. Use the audit as leverage to insert explicit virtualisation language into your contract. Get written agreement that your specific configuration (e.g., Oracle VMs pinned to a dedicated VMware cluster of N hosts) satisfies Oracle's licensing requirements. This eliminates ambiguity for future audits.
A global financial services firm ran Oracle Database Enterprise Edition on a 10-host VMware cluster (320 cores total). Oracle's audit findings demanded 160 processor licences at list price — a $7.6M exposure. Our team analysed the firm's OMA and identified that the Partitioning Policy was not referenced in any signed agreement. We documented that Oracle was only installed on 2 hosts within the cluster, that DRS was disabled for Oracle VMs, and that operational controls prevented migration. After six months of negotiation, the firm purchased 8 processor licences covering only the 2 dedicated Oracle hosts — a total cost of $380,000. Oracle closed the audit with a compliance letter.
✓ $7.2M in audit exposure eliminated through contract-based defenceOracle Audit Defence Playbook: Contract-Based Strategies for Virtualisation Disputes
Step-by-step frameworks for challenging Oracle's Partitioning Policy in audits — with contract analysis templates, documentation checklists, and negotiation scripts.
Download White Paper →7. The Cost Impact: Soft vs Hard Partitioning — Real-World Scenarios
The financial difference between soft and hard partitioning is not marginal — it is often the difference between a manageable IT budget and a crisis. These scenarios use Oracle Database Enterprise Edition list pricing ($47,500 per processor licence, 22% annual support). For the complete financial analysis, see Oracle Partitioning Policy Cost Impact: Real-World Scenarios.
Scenario A: Soft Partitioning — 10-Host VMware Cluster
🚫 VMware Cluster (Oracle's Soft Partitioning Rule)
Scenario B: Hard Partitioning — Oracle Linux KVM with CPU Pinning
✅ Oracle Linux KVM with Hard Partitioning (8 Pinned Cores)
Scenario C: Dedicated VMware Cluster (Compromise Approach)
✅ Dedicated 2-Host VMware Cluster for Oracle
Even the compromise approach (Scenario C) saves $6 million compared to licensing the full 10-host cluster. Hard partitioning (Scenario B) saves over $9 million. These are not theoretical numbers — this is the actual cost calculus Oracle applies in audits. For database licensing models and pricing details, see our Oracle Database Licensing Guide.
📊 How Much Is Your Virtualisation Costing You in Oracle Licences?
We calculate the exact licence exposure for your virtualised environment and design architectures that reduce costs by 40-90% — without compromising performance or availability.
8. Virtualisation-Specific Guidance: VMware, Hyper-V, Nutanix, Containers
| Platform | Oracle Classification | Audit Approach | Key Risk | Best Practice |
|---|---|---|---|---|
| VMware vSphere | Soft partitioning | Oracle has vCenter scripts — automated data collection | vMotion/DRS enables VM mobility; Oracle demands all-host licensing | Dedicated Oracle cluster with DRS/vMotion disabled |
| Microsoft Hyper-V | Soft partitioning | Manual data collection; Oracle requests Hyper-V configuration exports | Live Migration and failover clustering expand scope | Isolate Oracle on dedicated hosts; disable Live Migration for Oracle VMs |
| Nutanix AHV | Soft (by omission) | No official AHV script; Oracle requests Prism reports | AHV live migration + Prism Central "galaxy licensing" risk | Dedicated Nutanix cluster; separate Prism management |
| Docker / Containers | Soft partitioning | Oracle requests host and orchestration details | Container scheduling can place Oracle on any host | Pin Oracle containers to dedicated nodes; licence those nodes |
| Kubernetes (K8s) | Soft partitioning | Oracle requests cluster node inventory | K8s scheduler can place Oracle pods on any node | Dedicated node pool for Oracle with taints/tolerations |
| Oracle VM (OVM) | Hard partitioning | Oracle accepts OVM Manager config as evidence | Must have CPU pinning; without it = soft partitioning | Use OVM with documented CPU pinning; archive configs |
| Oracle Linux KVM | Hard partitioning | Oracle accepts config files showing CPU affinity | Must demonstrate fixed CPU binding, not dynamic | Set vcpupin in libvirt; document and archive |
For detailed platform-specific guidance: Oracle licensing on VMware | Oracle licensing on Hyper-V | Oracle licensing on Nutanix | Oracle licensing in virtualised environments (comprehensive guide)
9. 10 Strategies to Reduce Licensing Exposure Under the Partitioning Policy
- Isolate Oracle on a dedicated, small cluster. Whether you use VMware, Hyper-V, or Nutanix, creating a physically separate cluster of 2-3 hosts exclusively for Oracle workloads is the single most effective cost reduction strategy. You licence only the dedicated cluster — not your entire virtualisation estate.
- Implement hard partitioning where feasible. If your infrastructure supports Oracle VM or Oracle Linux KVM, migrating Oracle workloads to a hard-partitioned environment can reduce licence requirements by 80-95%. The upfront migration cost is negligible compared to the licence savings. See our implementation guide.
- Choose nodes with fewer, smaller-core processors. Every core in the Oracle cluster must be licensed. Use nodes with lower core counts (e.g., 2 × 8-core sockets instead of 2 × 16-core) to minimise the Core Factor denominator. The performance trade-off is often negligible for database workloads.
- Evaluate Named User Plus (NUP) licensing. For applications with limited, known user populations, NUP licensing can be 30-50% cheaper than Processor licensing — even with the per-processor minimum of 25 NUP. Conduct a thorough user census before committing.
- Audit database options and management packs quarterly. Oracle Database options (Partitioning, Advanced Security, Diagnostics Pack, Tuning Pack, etc.) each require separate licences across the same scope as the database. Run
SELECT * FROM DBA_FEATURE_USAGE_STATISTICS WHERE CURRENTLY_USED='TRUE'on every database and disable anything you haven't licensed. - Consider Oracle Standard Edition 2 (SE2). SE2 uses socket-based licensing (not core-based) at roughly $17,500 per socket — a fraction of Enterprise Edition's cost. If your workload fits within SE2's constraints (max 2 sockets, 16 threads, no advanced options), the savings are dramatic.
- Negotiate explicit virtualisation terms into your Oracle contract. During renewals or new purchases, insert language that defines your specific virtualised configuration as compliant. Get written acknowledgement that your dedicated VMware cluster of N hosts satisfies Oracle's requirements. This eliminates Partitioning Policy disputes in future audits.
- Maintain audit-ready documentation at all times. Keep current cluster diagrams, host inventories, VM placement records, migration logs, Core Factor calculations, and licence entitlement spreadsheets. If Oracle can't challenge your documentation, they can't challenge your position.
- Conduct annual internal mock audits. Run Oracle's LMS Collection Tool scripts yourself and compare the output against your entitlements. Fix discrepancies proactively — at your own pace, on your own terms. An internal audit costs a fraction of what an Oracle-led audit costs in settlements.
- Engage independent Oracle licensing experts before an audit. The time to build your defence is before Oracle sends the audit letter — not after. Former Oracle auditors know exactly how LMS/GLAS approaches virtualisation findings, what evidence is persuasive, and where Oracle's position is weakest. This expertise pays for itself many times over.
A global manufacturing company ran Oracle Database and middleware across a shared 8-host VMware cluster with 256 total cores. Oracle's soft partitioning rule required 128 processor licences — over $6M in licence costs. We designed a migration to a dedicated Oracle Linux KVM server with 16 cores, hard-partitioned with CPU pinning to allocate 8 cores to Oracle. The licence requirement dropped to 4 processor licences — a saving of $5.9M in licences. After factoring in migration costs and the new KVM server, the net saving was $4.8M. Annual support costs dropped by $1.1M.
✓ $4.8M net savings through hard partitioning migration🔒 Want to Reduce Your Oracle Virtualisation Licensing Costs?
We design architectures that align with Oracle's partitioning rules while minimising licence exposure. From hard partitioning implementations to audit defence strategies — we handle it all.
Frequently Asked Questions
📚 Related Reading
Do You Want to Know More About Our Oracle Advisory Services?
Fredrik Filipsson
Fredrik brings 20+ years of enterprise software licensing expertise, including 9 years working directly for Oracle. He has personally advised on 200+ Oracle audit defence engagements across Fortune 500 organisations and leads Redress Compliance's Oracle practice, specialising in virtualisation licensing, partitioning policy disputes, and contract negotiation.