Introduction to Oracle Licensing on IBM LPAR
Oracle has divided sub-capacity technology into two categories, soft and hard partitioning.
Oracle approves hard partitioning technologies as a means of sub-capacity licensing. IBM LPAR is approved by Oracle as hard partitioning giving you the option to license per the virtual processor power that you assign to the Oracle deployment.
When it comes to deploying Oracle workloads on Logical Partitions (LPARs), you have two main options for Oracle licensing:
- Licensing the underlying physical hardware (Traditional core-based licensing)
- Using Oracle’s extra-contractual hard partitioning policy to license the LPAR
Oracle Licensing IBM on LPAR
Licensing the Hardware
Licensing the underlying hardware is quite simple. You need to count the cores where Oracle software is installed and/or running, apply the core factor, and that gives you the required licenses. However, with LPARs, it gets tricky because a frame can have multiple processor pools.
LPARs can exist in different pools and can potentially move between pools. If LPARs are associated with a processor pool and set up so they never leave that pool, then you can count the number of cores in the pool to determine licensing liability.
But if the LPARs are allowed to move around, it gets complicated, and you have to count all processors where the LPARs have run.
Licensing with the Oracle Partitioning Policy
The other method for licensing LPARs is to use the guidelines described in the partitioning policy. Here are the key points:
- Dedicated LPARs are allowed
- If using micro-partitioned LPARs, the following conditions must be met:
- The LPAR must be capped
- Live Partition Mobility (LPM) must be disabled
- TurboCore mode is not permitted
For a dedicated LPAR, count the number of virtual processors toward license usage. A dedicated LPAR with two virtual processors can use up to 100% of two physical cores.
With a micro-partitioned LPAR, it’s more complex. To use Oracle’s Partitioning Policy, the LPAR must be capped. You count the entitled capacity, or entitlement, towards license usage. However, the entitlement can be specified as a decimal, so we need to round up to count the number of processors in use. For example, a capped, micro-partitioned LPAR with two virtual processors and an entitlement of 1.4 is counted as two cores toward license usage.
Remember, with micro-partitioned LPARs, LPM must be turned off. If an LPAR moves from one pool to another, it only runs on one pool at a time. From a licensing standpoint, this is considered a de-install and re-install of the license for that LPAR, incurring a licensing liability only on one pool at a time. However, since LPM must be disabled to take advantage of the partitioning policy, this fact doesn’t apply.
Licensing Strategy
Since there are different options for licensing on PowerVM, you should carefully consider your licensing strategy. When licensing the hardware, use processor pools to limit the license count.
Keep in mind that different pools can be configured for different Oracle products. One pool can be dedicated to Enterprise Edition, whereas another pool may be used with Enterprise Edition plus Partitioning. No matter the strategy, ensure the LPARs don’t move around, or more licenses will be consumed.
Summary
Understanding the intricacies related to Oracle licensing on PowerVM is crucial. This topic continues to come up at Redress Compliance as we work with clients running on PowerVM.
Unraveling some of the mysteries behind the PowerVM hypervisor is critical to understanding the related Oracle licensing implications.
Frequently Asked Questions
What are the two main options for Oracle licensing on LPARs?
- Licensing the underlying physical hardware (Traditional core-based licensing)
- Using Oracle’s extra-contractual hard partitioning policy to license the LPAR
What happens when LPARs are allowed to move around in the processor pool?
If the LPARs are allowed to move around, it gets complicated, and you have to count all processors where the LPARs have run.
What are the conditions to meet when using micro-partitioned LPARs?
- The LPAR must be capped
- Live Partition Mobility (LPM) must be disabled
- TurboCore mode is not permitted
How is the license usage counted for a dedicated LPAR and a micro-partitioned LPAR?
- For a dedicated LPAR, count the number of virtual processors toward license usage. A dedicated LPAR with two virtual processors can use up to 100% of two physical cores.
- For a micro-partitioned LPAR, count the entitled capacity, or entitlement, towards license usage. If the entitlement is specified as a decimal, round up to count the number of processors in use.
What should be kept in mind while formulating a licensing strategy on PowerVM?
Use processor pools to limit the license count and configure different pools for Oracle products. Ensure the LPARs don’t move around, or more licenses will be consumed.
Where Can I read about this licensing rule/policy?
You can read the Oracle partitioning policy document.
Need Help with Oracle Licensing on IBM LPAR?
Navigating the complexities of Oracle licensing on IBM LPAR can be challenging. But you don’t have to do it alone. At Redress Compliance, we specialize in helping clients understand and manage their Oracle licenses effectively.
Whether you’re just starting with Oracle licensing or looking to optimize your existing setup, our team of experts is here to assist. We can help you unravel the intricacies of Oracle licensing, formulate effective strategies, and ensure you’re getting the most out of your Oracle products.
