Hard Partitioning to Reduce CPU Licensing Costs
Oracle allows customers to license a subset of CPU cores on a physical server—but only if they use an Oracle-approved method known as “hard partitioning.” Understanding Oracle’s policy on hard partitioning is critical for correctly managing license costs and ensuring compliance.
This guide clearly explains:
- What Oracle considers “hard partitioning.”
- Approved methods recognized by Oracle.
- Common methods Oracle does not accept (“soft partitioning”).
- Clear practical examples to illustrate valid and invalid scenarios.
Read our Oracle Database Licensing FAQs.
Can You License Only Certain CPU Cores for Oracle?
Clearly:
- Yes, but only through approved “hard partitioning” methods.
- No, if using “soft partitioning” or non-approved virtualization methods.
Oracle explicitly defines which partitioning methods are acceptable. Using unapproved methods does not reduce licensing requirements.
Hard vs. Soft Partitioning for Oracle Licensing: Clearly Explained
Oracle clearly distinguishes between two types of CPU partitioning:
- Hard Partitioning (Approved by Oracle):
- Physical or virtualization methods Oracle explicitly recognizes.
- It allows licensing only the subset of cores dedicated to Oracle workloads.
- Soft Partitioning (Not Approved by Oracle):
- Virtualization methods Oracle does not recognize for license reduction.
- It requires the licensing of all available cores, regardless of actual usage.
Oracle’s Approved Hard Partitioning Methods
Oracle explicitly approves specific virtualization and partitioning technologies:
- Oracle VM Server (OVM) has pinned vCPUs.
- Oracle Linux KVM is configured with hard partitioning.
- Solaris Zones (Capped Zones) explicitly limit core usage.
- IBM LPAR (Logical Partitioning) clearly defined hardware partitions.
These methods explicitly isolate cores for Oracle software. Oracle agrees that you can license only these dedicated cores.
Clearly Explained Example:
- 16-core physical server using Oracle VM Server:
- Assigning a VM clearly to 4 specific cores allows licensing just these 4.
Read Oracle Database Processor Licensing: Definition and Calculation.
Methods Oracle Does NOT Accept (Soft Partitioning)
Oracle explicitly classifies several virtualization methods as “soft partitioning,” meaning no reduction in licensing:
- VMware vSphere (ESXi)
- Microsoft Hyper-V
- Docker/Kubernetes CPU shares or limits
- Any software-based CPU throttling
Even if these methods limit cores or vCPUs at runtime, Oracle explicitly requires licensing the entire physical server or cluster.
Clearly Explained Example:
- 16-core physical server using VMware ESXi:
- Assigning a VM limited to 4 cores still requires licensing all 16 cores.
Practical Examples Comparing Hard vs. Soft Partitioning
| Partitioning Method (Clearly Explained) | Cores Allocated | Partitioning | Cores licensed |
|---|---|---|---|
| Oracle VM Server (Pinned vCPUs) | 4 of 16 cores | ✅ Yes (Hard Partitioning) | 2 cores licensed |
| Oracle Linux KVM (Hard Partitioned) | 8 of 32 cores | ✅ Yes (Hard Partitioning) | 8 cores are licensed |
| Solaris Zones (Capped) | 2 of 8 cores | ✅ Yes (Hard Partitioning) | 2 cores licensed |
| IBM LPAR (Hardware Partitioned) | 6 of 24 cores | ✅ Yes (Hard Partitioning) | 2 cores are licensed |
| VMware vSphere (Soft Partitioning) | 4 of 16 cores | ❌ No (Soft Partitioning) | all 16 cores licensed |
| Docker CPU Limits (Soft Partitioning) | 2 of 8 cores | ❌ No (Soft Partitioning) | 6 cores are licensed |
Oracle Licensing Best Practices Clearly Explained
To limit Oracle CPU licensing, follow these best practices:
✅ Use Oracle-approved hard partitioning methods (Oracle VM Server, Oracle Linux KVM, Solaris Zones, IBM LPAR).
✅ Document your partitioning setup and the assigned cores explicitly.
✅ Avoid “soft partitioning” methods (VMware, Hyper-V, and Docker CPU limits) if license reduction is your goal.
✅ Consult Oracle’s official documentation to verify the approved methods.
Common Misunderstandings Corrected Clearly
- Misconception: “VMware vSphere with limited vCPUs reduces Oracle licenses.”
- Reality: Oracle explicitly classifies VMware as soft partitioning—clearly no license reduction permitted.
- Misconception: “CPU pinning on Docker containers counts as hard partitioning.”
- Reality: Docker CPU limits are considered soft partitioning—requires licensing all cores.
- Misconception: “Any virtualization method reduces Oracle licensing if vCPUs are limited.”
- Reality: Only Oracle’s explicitly approved methods qualify as hard partitioning.
Licensing Compliance Checklist for Hard Partitioning
✅ Verify that ur partitioning method is explicitly Oracle-approved for license reduction.
✅ Document dedicated cores and configurations clearly for audit purposes.
✅ Avoid virtualization methods Oracle clearly defines as soft partitioning.
✅ Review and confirm Oracle’s published guidelines regularly.
Conclusion: Understanding Oracle Hard Partitioning Licensing
Oracle permits sub-capacity licensing only through approved hard partitioning methods. Understanding Oracle’s definitions—what’s explicitly approved (Oracle VM Server, Oracle Linux KVM, Solaris Zones, IBM LPAR) and what’s clearly not (VMware, Hyper-V, Docker)—ensures compliance and accurate cost management.
By following Oracle’s policies and guidelines, you avoid licensing pitfalls, audit complications, and unexpected costs, optimizing your Oracle software investment.
