Oracle Soft vs. Hard Partitioning

Oracle Soft vs. Hard Partitioning

• Soft Partitioning: Flexible, dynamic resource allocation. License all physical hosts.
• Hard Partitioning: Fixed, rigid resource boundaries. Only assigned resources need licensing.
• Recognition: Oracle does not recognize soft partitioning for limiting licenses but approves hard partitioning.
• Cost: Soft partitioning leads to higher licensing costs compared to hard partitioning.

Oracle Soft vs. Hard Partitioning

Understanding the concepts of soft and hard partitioning is crucial when managing Oracle licensing in virtualized environments. These partitioning strategies are key factors that influence how Oracle software should be licensed, directly affecting costs, compliance, and overall software management.

This guide delves into the nuances of Oracle soft and hard partitioning, helping you more effectively navigate the complexities of Oracle licensing policies.

Oracle Soft Partitioning

Oracle Soft Partitioning refers to virtualization technologies that Oracle does not recognize for limiting software license requirements. These virtualization methods enable flexible resource allocation, allowing virtual machines to move dynamically across multiple physical servers.

This makes it difficult to limit the number of processors hosting Oracle software.

Key Characteristics of Soft Partitioning:

• Dynamic Resource Allocation: Soft partitioning allows resources to be dynamically allocated or moved between virtual machines and servers.
• Licensing Requirement: Oracle requires all physical hosts within a cluster to be licensed, regardless of how much of the server’s resources are used by Oracle software.
• Non-Recognition: Oracle does not recognize soft partitioning as a way to limit licensing obligations. This means that even if Oracle runs on just a small part of a cluster, the entire cluster must be licensed.

Common Soft Partitioning Technologies:

• VMware vSphere (ESXi)
• Microsoft Hyper-V
• KVM (Kernel-Based Virtual Machine)
• Oracle VirtualBox

Example: Imagine running Oracle Database on a VMware ESXi cluster of ten hosts. Oracle considers VMware a soft partitioning technology, which means you must license all ten hosts, regardless of whether Oracle is running on just one or a few of those hosts.

Oracle Hard Partitioning

Oracle Hard Partitioning is a technique that Oracle recognizes for limiting software license requirements. With hard partitioning, the hardware is physically segmented into smaller units, and each unit can be licensed independently.

This rigid and fixed method ensures Oracle workloads are confined to specific, isolated hardware resources.

Key Characteristics of Hard Partitioning:

• Fixed Resource Allocation: Hard partitioning provides a rigid division of resources that do not overlap or migrate dynamically.
• Licensing Requirement: Only the physical resources allocated to Oracle workloads must be licensed, potentially saving costs.
• Oracle-Approved: Oracle explicitly recognizes certain technologies as legitimate methods for limiting license obligations.

Approved Hard Partitioning Technologies:

• Oracle VM Server for x86 (OVM)
• IBM LPAR (Logical Partitioning)
• Solaris Zones (Capped Zones)
• HP vPar and nPar
• Fujitsu PPAR

Example: Consider a company using IBM LPAR to run Oracle applications. The server has 16 cores, but only 4 are assigned to the Oracle environment. In this case, only the four cores must be licensed, significantly reducing licensing costs.

Key Differences Between Soft and Hard Partitioning

Understanding the fundamental differences between soft and hard partitioning is essential for effective Oracle license management. Here is a detailed comparison:

Key Takeaway: Soft partitioning is more flexible but has higher licensing costs, while hard partitioning offers cost savings through fixed resource assignments, which Oracle acknowledges.

Technologies Approved for Soft and Hard Partitioning

Oracle has published clear guidelines regarding which technologies are considered soft or hard partitioning.

Below is a list of approved and non-approved technologies:

Technologies for Soft Partitioning:

• VMware vSphere (ESXi): Oracle classifies VMware as soft partitioning, meaning you must license all hosts within the cluster.
• Microsoft Hyper-V: Hyper-V also falls under soft partitioning, subjecting it to the same licensing requirements as VMware.
• KVM: As an open-source virtualization option, Oracle also considers KVM soft partitioning.

Technologies for Hard Partitioning:

• Oracle VM Server for x86: Recognized by Oracle when configured properly to cap the number of resources.
• IBM LPAR: Logical partitioning on IBM systems, provided it is configured for cap usage.
• Solaris Zones: Capped Zones are considered hard partitioning, limiting the processors available for Oracle workloads.

Table: Approved and Non-Approved Technologies

Oracle Licensing Requirements for Soft and Hard Partitioning

The difference in licensing requirements for soft and hard partitioning can lead to a significant impact on costs:

• Soft Partitioning Licensing: Oracle requires that all processors in every physical host within a cluster be licensed, even if the Oracle software runs only on a subset of those hosts. This can significantly increase licensing costs, especially for large environments.
• Hard Partitioning Licensing: Only the processors or cores explicitly assigned to run Oracle software must be licensed. If you use a technology like IBM LPAR and limit Oracle to 4 cores out of a possible 16, only those four cores need to be licensed, leading to more manageable costs.

Example of Licensing Cost Impact: Imagine a VMware cluster containing ten hosts containing 16 cores. If Oracle runs on any virtual machine in this cluster, Oracle requires licensing for all 160 cores. Conversely, if you use hard partitioning with Oracle OVM and assign eight cores to Oracle, you only need to license those eight cores.

Common Misconceptions

There are several misconceptions about Oracle soft and hard partitioning that can lead to costly licensing mistakes:

• “Affinity Rules Limit Licensing”: Many believe that setting Affinity Rules in VMware or Hyper-V to limit Oracle workloads to specific hosts will limit licensing. Oracle does not recognize affinity rules as a valid way to limit licenses; all physical hosts must be licensed.
• “Only Active Hosts Need Licensing”: A common misunderstanding is that only the hosts actively running Oracle require licensing. According to Oracle, all hosts must be licensed if there is mobility within the cluster (like vMotion).
• “Hard Partitioning is Easy to Configure”: Hard partitioning must be meticulously configured to create fixed boundaries. Misconfigurations can cause Oracle to deem the entire server eligible for licensing, leading to significant compliance risks.

Practical Examples of Soft and Hard Partitioning

Example 1: VMware (Soft Partitioning)

• Scenario: A company runs Oracle Database in a VMware vSphere environment with 15 hosts.
• Licensing Requirement: Although VMware is used on only a few virtual machines, Oracle considers it a soft partitioning technology. As a result, all 15 hosts must be licensed.

Example 2: IBM LPAR (Hard Partitioning)

• Scenario: An organization uses IBM Power Systems with 32 cores, and it allocates six cores to run the Oracle Database using LPAR.
• Licensing Requirement: Since LPAR is a recognized hard partitioning technology, only the six cores dedicated to Oracle need to be licensed.

How to Choose the Right Strategy

Choosing between soft and hard partitioning depends on various factors, including cost considerations, IT infrastructure, and business needs.

Here are some pointers to help you decide:

• Cost Considerations: If you want to limit licensing costs and have control over physical resources, hard partitioning may be the better choice.
• Flexibility Needs: With its flexibility and dynamic resource allocation, soft partitioning is better suited for environments where workloads shift frequently. However, licensing can be more expensive.
• Compliance Requirements: Ensure that your partitioning method meets Oracle’s licensing policies. Failure to comply can result in significant fines and back charges.

Best Practices for Managing Oracle Licensing

To effectively manage Oracle licensing with partitioning, follow these best practices:

1. Use Oracle-Approved Technologies: When considering hard partitioning, stick to Oracle-approved technologies like OVM or LPAR to ensure compliance.
2. Proper Configuration: Incorrectly configuring hard partitioning can lead to non-compliance. Always follow Oracle’s guidelines meticulously and ensure that resources are capped appropriately.
3. Document Everything: Whether using soft or hard partitioning, documentation is key. Maintain detailed records of resource assignments and ensure proper documentation during audits.
4. Internal Audits: Conduct regular internal audits of your virtualization configurations to ensure compliance. This helps identify issues before Oracle conducts an official audit.
5. Consult Licensing Experts: Oracle licensing is complex, and any mistakes can be costly. Engage with Oracle licensing experts to ensure your configurations are compliant and cost-effective.

Key Takeaways

• Soft Partitioning allows dynamic resource allocation but requires licensing for all hosts within a cluster, making it costlier.
• Hard Partitioning creates fixed resource boundaries, allowing organizations to license only the assigned resources, potentially saving costs.
• Choosing between soft and hard partitioning depends on cost, compliance, and flexibility.
• Compliance is crucial. Only Oracle-approved technologies for hard partitioning should be used to reduce licensing obligations.
• Proper documentation and expert advice are critical to managing Oracle licenses effectively in partitioned environments.

Final Tip: Understanding Oracle partitioning policies is essential for reducing costs and ensuring compliance. Stay informed about Oracle’s latest guidelines and work with experts to ensure your strategy meets licensing requirements.

Oracle Soft vs. Hard Partitioning FAQ

What is Oracle Soft Partitioning? Oracle Soft Partitioning refers to virtualization technologies that allow dynamic resource allocation across a cluster. However, Oracle does not recognize this method for reducing licensing requirements, meaning all physical hosts in the cluster must be licensed.

What is Oracle Hard Partitioning? Oracle Hard Partitioning uses hardware-based or fixed software configurations to create rigid resource boundaries. Oracle recognizes hard partitioning for limiting the required licenses to only the allocated physical resources.

How does Oracle treat VMware in partitioning? Oracle treats VMware as a soft partitioning technology, meaning all physical hosts in a VMware cluster must be licensed, regardless of where the Oracle software is running.

Which technologies are approved for Hard Partitioning? Oracle officially approves Oracle VM Server for x86, IBM LPAR, Solaris Zones, HP vPar, and Fujitsu PPAR as hard partitioning technologies.

What is the difference between Soft and Hard Partitioning? The main difference is resource allocation. Soft partitioning allows the dynamic movement of resources, while hard partitioning provides fixed resource boundaries. Oracle only recognizes hard partitioning to limit license requirements.

Does Oracle recognize Soft Partitioning for licensing? No, Oracle does not recognize soft partitioning technologies as valid methods for limiting licensing requirements. All physical servers in a cluster must be licensed, regardless of the number of Oracle instances running.

Can Affinity Rules be used to limit Oracle licensing? No, Oracle does not recognize using Affinity Rules in VMware or Hyper-V to bind Oracle workloads to specific hosts as a valid method for limiting licenses.

Is Oracle VM Server for x86 Hard Partitioning? When configured properly to cap the resources allocated for Oracle workloads, Oracle VM Server for x86 (OVM) is considered hard partitioning.

How does licensing work with Hard Partitioning? With hard partitioning, you only need to license the processors or cores specifically allocated to run Oracle software. This can lead to significant cost savings compared to licensing all resources in a cluster.

Does Hard Partitioning reduce Oracle licensing costs? Yes, it does. It limits the number of processors or cores licensed to those specifically allocated for Oracle workloads.

Why is Soft Partitioning more expensive? Soft partitioning is more expensive because Oracle requires licensing for all physical hosts within a cluster, even if it runs on just one of them. This often leads to over-licensing.

Can Solaris Zones be used for Oracle licensing? Yes, Solaris Zones, specifically capped Zones, are approved by Oracle for hard partitioning, allowing organizations to limit the number of processors that need to be licensed for Oracle software.

Can Hard Partitioning be used with hyper-converged infrastructure? It is challenging and requires strict configuration to ensure fixed resource boundaries that comply with Oracle’s guidelines.

Oracle recognizes Microsoft Hyper-V as Hard Partitioning. No, Oracle considers it a soft partitioning technology, meaning all hosts in a Hyper-V cluster must be licensed.

How do I choose between Soft and Hard Partitioning? The choice depends on your need for cost control versus resource flexibility. Hard partitioning is ideal for reducing licensing costs, while soft partitioning is better for environments requiring dynamic resource allocation.

Do you want to know more about our Oracle License Management Services?

Please enable JavaScript in your browser to complete this form.

Name *

Email *

Company

Message *

Submit