Oracle Soft Partitioning
- Virtualization method not recognized for limited licenses.
- Requires licensing of all physical hosts in a cluster.
- Technologies include VMware, Hyper-V, KVM, and VirtualBox.
- It is not contractually binding; it is only advisory per Oracle guidelines.
- Offers flexibility but comes with increased licensing costs.
What is Oracle Soft Partitioning?
Oracle Soft Partitioning refers to using certain virtualization technologies and techniques that Oracle does not recognize to limit software license requirements.
In simpler terms, Oracle categorizes these methods as insufficient to partition hardware in a way that restricts how Oracle software is licensed. As a result, organizations using soft partitioning must license all physical servers involved, regardless of how Oracle software is allocated or configured within the virtual environment.
Understanding Oracle’s approach to soft partitioning is crucial for managing Oracle licenses, particularly for organizations that utilize popular virtualization platforms like VMware, Hyper-V, or KVM.
Unlike hard partitioning (which Oracle recognizes as a legitimate way to limit the scope of license requirements), soft partitioning can lead to significant and unexpected licensing costs if not managed correctly.
Oracle’s View on Soft Partitioning
Oracle has a strict licensing policy for virtualization, particularly soft partitioning. Soft partitioning encompasses a range of virtualization techniques that allow workloads to be dynamically moved across servers or allow virtual machines to use flexible resources from a larger cluster.
According to Oracle, soft partitioning methods do not guarantee a fixed assignment of resources to an Oracle instance, which means Oracle can theoretically run on all hosts in a virtual environment.
Here’s a summary of Oracle’s standpoint:
- All Hosts Must Be Licensed: If soft partitioning is used, Oracle requires you to license all physical hosts in the cluster where Oracle software could potentially run, even if it is running on just one or two hosts.
- Resource Allocation: Technologies that allow resource sharing or dynamic reallocation of resources are classified as soft partitioning. Oracle insists that the software can be moved to any server in the cluster, and thus, all such servers must be licensed.
- Policy Document Disclaimer: Oracle’s Partitioning Policy Document explicitly states that soft partitioning cannot be used to determine or limit the number of required software licenses. The policy document is, however, not a legally binding contract, but it is a guide Oracle uses during audits.
Example: Imagine you have a VMware ESXi cluster with ten hosts, but Oracle software only runs on one of them. Oracle’s position is that you must license all ten hosts, as the software can be migrated to any host.
Examples of Soft Partitioning Technologies
Oracle considers a range of popular virtualization technologies as soft partitioning. Here are some of the most common technologies and their implications for Oracle licensing:
- VMware vSphere (ESXi)
- VMware is probably the most commonly used virtualization platform in enterprise environments. However, Oracle considers VMware vSphere a soft partitioning technology, meaning all cluster hosts must be licensed.
- vMotion: VMware’s use of vMotion to migrate virtual machines from one host to another is a key reason why Oracle categorizes it as soft partitioning. vMotion allows Oracle software to theoretically run on any host in the cluster.
- Microsoft Hyper-V
- Like VMware, Microsoft Hyper-V allows virtual machines to be moved across multiple hosts. This flexibility classifies Hyper-V as a soft partitioning technology, according to Oracle.
- Even if you use Affinity Rules to keep Oracle workloads on specific hosts, Oracle still does not recognize this as a valid method to limit licensing.
- KVM (Kernel-Based Virtual Machine)
- KVM is an open-source virtualization technology widely used in Linux environments. Oracle treats KVM as a soft partitioning method, which means that all servers in a cluster running KVM must be licensed for Oracle software.
- Oracle VirtualBox
- Surprisingly, even Oracle’s own VirtualBox is considered a soft partitioning method. As such, using VirtualBox does not limit licensing requirements.
Table: Soft Partitioning Technologies and Licensing Requirements
| Technology | Soft Partitioning | Oracle Licensing Requirement |
|---|---|---|
| VMware vSphere (ESXi) | Yes | License all physical hosts in the cluster and across vCenters. |
| Microsoft Hyper-V | Yes | License all physical hosts in the cluster |
| KVM | Yes | License all physical hosts in the cluster |
| Oracle VirtualBox | Yes | License all physical hosts in the cluster |
Oracle’s Licensing Requirements for Soft Partitioning
The core issue with soft partitioning technologies lies in Oracle’s licensing requirements. These requirements are often perceived as overly restrictive and costly. Here is what you need to know:
- License All Physical Processors: With soft partitioning, Oracle requires you to license all physical processors on each host in the entire cluster where Oracle software could run. This often results in licensing more processors used by Oracle workloads.
- Dynamic Resource Allocation: If your virtualization platform supports dynamic resource allocation, you must license all hosts since Oracle assumes its software can run on any of those servers.
- Lack of Flexibility: Oracle’s stance limits the cost savings typically associated with virtualization. Virtualization is usually seen as a way to make IT more efficient, but Oracle’s licensing policies effectively negate the cost benefits of running Oracle on soft partitioned environments.
Example: Suppose you have a cluster of 20 physical servers running Microsoft Hyper-V. Even if Oracle is only running on a single virtual machine pinned to a specific host, Oracle requires you to license all 20 servers, significantly increasing licensing costs.
Common Misconceptions About Soft Partitioning
There are a few misconceptions about soft partitioning that can lead to costly mistakes in Oracle environments. Let’s clear up some of the most common misunderstandings:
- “Affinity Rules Can Limit Licensing”: Many organizations believe that using Affinity Rules or anti-affinity settings in VMware or Hyper-V can help limit the required licenses. Oracle, however, does not accept affinity rules as a valid method for limiting licenses, meaning all hosts must still be licensed.
- “Only Active Hosts Need Licensing”: A frequent misconception is that only hosts actively running Oracle workloads must be licensed. According to Oracle, if the software has mobility within a cluster, all physical hosts are subject to licensing.
- “The Partitioning Policy Document is Binding”: It is essential to understand that Oracle’s Partitioning Policy Document is not part of your licensing contract. Although it is a guideline during audits, it is not legally enforceable unless specifically referenced in your contract.
Strategies to Manage Licensing with Soft Partitioning
Given the strict requirements around soft partitioning, organizations must take a strategic approach to effectively manage their Oracle licensing costs.
Here are some potential strategies:
- Dedicated Clusters for Oracle
- One of the most effective ways to manage licensing costs is to create dedicated clusters for Oracle workloads. By keeping Oracle isolated in its cluster, you avoid the need to license all servers across a larger, shared infrastructure.
- Contractual Negotiations with Oracle
- Consider negotiating more favorable terms for virtualized environments during contract renewals or new purchases. If you have substantial leverage, Oracle may sometimes agree to customized terms.
- Oracle ULA (Unlimited License Agreement)
- An Oracle ULA may help manage costs if you use Oracle extensively in a virtual environment. A ULA allows unlimited deployment of certain Oracle products for a defined period, but it comes with challenges during the certification process.
- Limit vMotion Capabilities
- If you use VMware, consider limiting vMotion capabilities for Oracle virtual machines. Although Oracle still doesn’t officially accept this, limiting vMotion can help build a case in which Oracle workloads are confined to specific hosts.
- Consider Hard Partitioning
- Where possible, consider using hard partitioning technologies approved by Oracle. These technologies, such as Oracle OVM or IBM LPAR, allow you to physically segment resources, limiting the number of licenses required.
Example Strategy: Imagine you have a large virtual environment running both Oracle and non-Oracle workloads. By creating a dedicated vSphere cluster just for Oracle and negotiating customized terms with Oracle to recognize the limited scope of the cluster, you could significantly reduce licensing costs.
Key Takeaways
- Oracle Soft Partitioning refers to virtualization methods that Oracle does not recognize for reducing licensing requirements. With soft partitioning, all physical hosts in the cluster must be licensed.
- Technologies like VMware, Hyper-V, and KVM are considered soft partitioning by Oracle and, therefore, have stricter licensing requirements.
- To manage costs effectively, consider strategies such as creating dedicated clusters, negotiating contract terms, or opting for Oracle ULAs where appropriate.
- Remember that Oracle’s Partitioning Policy Document is a guideline used during audits and is not legally binding unless referenced in your contract.
Final Tip: Navigating Oracle’s licensing policies in a virtualized environment can be challenging. Consult with Oracle licensing experts or legal advisors to ensure compliance and avoid costly surprises.
Read about Oracle Soft vs Hard Partitioning.
Oracle Soft Partitioning FAQ
What is Oracle Soft Partitioning? Oracle Soft Partitioning refers to the use of virtualization technologies that Oracle does not recognize as limiting the licensing scope for its software. This means that customers must license all physical hosts in a cluster.
Why is it called Soft Partitioning? It’s called “soft” because the virtualization method does not rigidly isolate resources to specific hosts, allowing potential movement of Oracle software across the cluster.
Is Oracle Soft Partitioning legally binding? No, Oracle’s Partitioning Policy is not legally binding. It is a guideline often referred to during audits but not part of the licensing contract.
What technologies are considered Soft Partitioning by Oracle? Technologies like VMware vSphere, Microsoft Hyper-V, KVM, and Oracle VirtualBox are all considered soft partitioning technologies by Oracle.
Does Oracle accept Affinity Rules to limit licenses? No, Oracle does not accept Affinity Rules or anti-affinity settings as a valid method to limit the required licenses in a soft partitioning environment.
Do all physical hosts need licensing under Soft Partitioning? Yes, Oracle requires that all physical hosts in the cluster where the Oracle software can potentially run must be licensed, not just the hosts currently running the software.
What is the difference between Hard and Soft Partitioning? Hard Partitioning physically segments resources and is accepted by Oracle for limiting licensing. Soft Partitioning is flexible, allowing movement between hosts, and is not accepted for limited licenses.
Is vMotion supported for limiting Oracle licenses? No. vMotion and similar technologies that allow the dynamic movement of virtual machines makes the entire cluster subject to licensing. Oracle does not accept these technologies to limit licensing requirements.
Soft partitioning is more costly for Oracle licensing. Oracle requires that all physical hosts in a soft partitioned cluster be licensed, which often results in licensing more processors used by Oracle workloads.
How can I reduce Oracle licensing costs with Soft Partitioning? Consider creating dedicated clusters for Oracle workloads to limit the number of servers needing licenses or negotiate custom contractual terms with Oracle to minimize costs.
Is VMware considered Soft Partitioning by Oracle? Yes, Oracle considers VMware a soft partitioning technology, meaning you will need to license all physical servers in a cluster, not just those currently hosting Oracle software.
Can I negotiate terms with Oracle regarding Soft Partitioning? Yes, during contract negotiations or renewals, you can attempt to negotiate custom terms that may help reduce the licensing burden associated with virtualized environments.
Should I use an Oracle ULA to manage Soft Partitioning? An Oracle ULA can provide unlimited deployment during the agreement period, which might help manage costs, but careful planning is needed for the certification phase.
Does Oracle’s Partitioning Policy apply globally? Yes, but it is subject to regional interpretations during audits. Always confirm compliance requirements with local Oracle representatives.
How do I defend against Oracle audits in a soft partitioning setup? Keep detailed documentation of Oracle deployments, limit vMotion capabilities where possible, and consider getting support from licensing experts to help present your case effectively during an audit.
