Oracle Licensing on IBM LPAR
- Core Counting: License all cores where Oracle runs.
- Static LPARs: License only the fixed pool of cores.
- Moving LPARs: License all pools where the LPAR has operated.
- Partitioning Policy: Micro-partitioning requires caps and LPM off.
- Rounding Rule: Round fractional entitlements to whole cores.
Oracle Licensing on IBM LPAR
Oracle licensing on IBM Logical Partitions (LPARs) involves specific rules under Oracle’s Partitioning Policy. Understanding these nuances ensures compliance and avoids licensing pitfalls, particularly in AIX environments.
1. Licensing Basics for Oracle on IBM LPARs
Core Counting
- Oracle licensing is determined by the number of processor cores where the Oracle software is installed or running.
- Core Factor Application: Use Oracle’s Core Factor Table to adjust the core count based on the processor type.
2. Licensing Challenges with LPARs
Multiple Processor Pools
IBM frames may have multiple processor pools, which can complicate licensing. The movement of LPARs between these pools plays a critical role in determining licensing requirements.
Static LPARs (Fixed Pools)
- If an LPAR is tied to a specific processor pool and does not move, only the cores within that pool are counted for licensing.
- Example: An LPAR fixed to a pool with eight cores requires eight processor licenses.
Moving LPARs (Across Pools)
- If an LPAR moves between multiple processor pools, Oracle licensing requires counting all processors in all pools where the LPAR has been active.
- Key Rule: You must license for the maximum potential capacity where the LPAR has operated, even if only temporarily.
Takeaway:
- For static LPARs, count cores in the designated pool.
- For moving LPARs, count cores across all pools where the LPAR has run.
3. Licensing Under Oracle Partitioning Policy
Oracle’s Partitioning Policy defines rules for licensing dedicated and micro-partitioned LPARs. Adherence to these rules is critical for remaining compliant.
Dedicated LPARs
- Permitted Use: Dedicated LPARs are allowed for Oracle licensing.
- License Calculation: Licensing is based on the number of virtual processors assigned to the LPAR.
- Example: A dedicated LPAR with two virtual processors requires two core licenses.
Micro-Partitioned LPARs
Micro-partitioning introduces additional restrictions under Oracle’s policy:
Conditions for Licensing:
- Resource Cap: The LPAR must have a fixed cap on resource usage (entitled capacity).
- Live Partition Mobility (LPM): LPM must be disabled. This means the LPAR cannot move between physical servers.
- TurboCore Mode: TurboCore mode is not permitted under Oracle’s licensing rules.
License Calculation:
- Licensing is based on the entitled capacity of the micro-partitioned LPAR.
- Rounding Rule: Round up fractional entitlements to the nearest whole number.
- Example: An LPAR with an entitlement of 1.4 cores is rounded up and counted as 2 cores for licensing purposes.
4. Special Considerations for Micro-Partitioned LPARs
Live Partition Mobility (LPM)
- If LPM is enabled and an LPAR moves between pools or servers, it is treated as a de-installation and re-installation of the Oracle license.
- However, under Oracle’s Partitioning Policy, LPM must be disabled for micro-partitioned LPARs. Thus, movement between pools is irrelevant for licensing.
Impact of Movement on Licensing
- If LPM is disabled as required, licensing liability applies only to the LPAR’s fixed entitled capacity.
- Key Clarification: Licensing remains limited to the configured entitlement, regardless of whether other pools exist.
5. Key Takeaways for Oracle Licensing on IBM LPARs
- Compliance: Track configurations and ensure adherence to Oracle’s Partitioning Policy to avoid compliance risks.
- Core Counting: Licensing is based on cores where Oracle software is installed or running, adjusted by Oracle’s Core Factor Table.
- Static vs. Moving LPARs:
- Static LPARs: License the cores in the specific, fixed pool.
- Moving LPARs: License the maximum potential capacity of all pools the LPAR has accessed.
- Dedicated LPARs: Count the number of virtual processors assigned to the LPAR.
Micro-Partitioned LPARs:
- Use entitled capacity for licensing.
- Round up fractional cores to the nearest whole number.
- LPM must be disabled, and TurboCore mode is not allowed.
Examples of Oracle Licensing Calculations on IBM LPAR
Oracle licensing on IBM LPAR systems depends on the core count, licensing metric (Processor or Named User Plus), and Oracle’s Core Factor Table. Below are practical examples for both static and micro-partitioned LPAR environments.
1. Processor-Based Licensing for Static LPARs
Scenario:
You have a static LPAR with eight virtual processors assigned. The processor type has a Core Factor of 0.75.
Calculation:
- Count the total virtual processors assigned to the LPAR: 8 virtual processors.
- Multiply by the Core Factor:
8×0.75 = 6 licenses
Result:
You need 6 Processor Licenses for Oracle on this LPAR.
2. Processor-Based Licensing for Micro-Partitioned LPARs
Scenario:
A micro-partitioned LPAR has an entitled capacity of 3.6 cores. The processor type has a Core Factor of 0.75.
Rules:
- Round up the fractional cores to the nearest whole number.
- Apply the Core Factor to the rounded-up core count.
Calculation:
- Round up the entitled capacity:
3.6 cores →4 cores - Multiply by the Core Factor:
4×0.75 = 3 licenses
Result:
You need 3 Processor Licenses for this micro-partitioned LPAR.
3. Named User Plus (NUP) Licensing for Static LPARs
Scenario:
You have a static LPAR with ten users accessing the Oracle Database. Oracle requires a minimum of 25 Named User Plus licenses per processor.
Details:
- The LPAR has 2 virtual processors.
- Oracle’s licensing rule states the minimum NUP count applies per processor.
Calculation:
- Determine the total minimum NUP licenses required:
2 processors × 25NUP = 50 NUP licenses - Compare the user count (10) with the minimum required (50).
Result:
You must license at least 50 Named User Plus licenses, even though only ten users are accessing the system.
4. Micro-partitioned LPAR with Multiple Entitlements
Scenario:
Two micro-partitioned LPARs share a server:
- LPAR 1: Entitled capacity of 2.4 cores
- LPAR 2: Entitled capacity of 3.2 cores
The processor has a Core Factor of 0.75.
Rules:
- Round up each LPAR’s entitlement.
- Calculate licenses for each separately.
Calculation:
- LPAR 1: Round up 2.4 cores → 3 cores.
3×0.75 = 2.25 → 3 licenses - LPAR 2: Round up 3.2 cores → 4 cores.
4×0.75 = 3 licenses - Combine the licenses:
3+3 = 6 Processor Licenses
Result:
You need 6 Processor Licenses for both LPARs combined.
5. LPAR Moving Between Pools
Scenario:
An LPAR moves between two processor pools:
- Pool A: 8 cores
- Pool B: 10 cores
- Core Factor: 0.75
Rule:
When an LPAR moves between pools, all cores must be licensed.
Calculation:
- Total cores across both pools:
8 cores + 10cores = 18cores - Apply the Core Factor:
18×0.75 = 13.5 → 14 licenses
Result:
You need 14 Processor Licenses for the LPAR moving between these pools.
Key Notes for Oracle Licensing
- Always round up fractional cores to the nearest whole number when calculating licenses for micro-partitioned LPARs.
- Use the Core Factor Table to determine adjusted core counts.
- For static LPARs, license only the cores within the specific processor pool.
- Moving LPARs requires licensing for all processors in every pool where they have operated.
You can accurately calculate costs and maintain compliance by carefully applying Oracle’s licensing rules to your environment.
Oracle Licensing on IBM LPAR FAQ
What is Oracle licensing on IBM LPAR based on?
Licensing is based on the number of cores where Oracle software is installed or running, adjusted using Oracle’s Core Factor Table.
How are static LPARs licensed?
Static LPARs tied to a specific processor pool require licensing for the cores in that dedicated pool.
How do moving LPARs impact Oracle licensing?
If an LPAR moves across multiple processor pools, you must license all cores in every pool where the LPAR has operated.
What is Oracle’s Partitioning Policy for IBM LPAR?
Oracle’s Partitioning Policy defines licensing rules for dedicated and micro-partitioned LPARs, including restrictions on LPM and core usage.
What are the requirements for micro-partitioned LPARs?
Micro-partitioned LPARs must have a capped entitlement, Live Partition Mobility (LPM) disabled, and TurboCore mode off.
How do I calculate licenses for micro-partitioned LPARs?
Licensing is based on the entitled capacity of the LPAR, rounded up to the nearest whole core.
What happens if an LPAR moves while LPM is enabled?
Movement with LPM enabled counts as a de-installation and re-installation, requiring licenses for all affected pools.
Is Oracle licensing different for dedicated LPARs?
Dedicated LPARs require licensing based on the total number of virtual processors assigned to the LPAR.
What does entitled capacity mean for LPAR licensing?
Entitled capacity refers to the fixed resource allocation (in cores) for a micro-partitioned LPAR, the basis for licensing.
How does rounding work for fractional core usage?
Fractional entitlements are rounded up to the nearest whole number for licensing purposes.
Does Oracle require all pools to be licensed in a frame?
Only pools where LPARs have been operational require licensing. Static LPARs are limited to their assigned pool.
How can I ensure compliance with Oracle’s licensing policy?
Ensure LPM is disabled, cap resource usage for micro-partitions, and license the correct number of cores according to Oracle’s rules.
What is Live Partition Mobility (LPM)?
LPM allows LPARs to move between physical servers. However, Oracle’s Partitioning Policy requires it to be disabled for compliance.
How does Oracle handle licensing virtual processors?
In dedicated LPARs, virtual processors are treated as physical cores for licensing purposes.
What happens during an Oracle licensing audit on IBM LPAR?
Oracle audits require you to prove compliance, including proper core counts, capped entitlements, and adherence to the Partitioning Policy.
