Oracle licensing on IBM platforms (like AIX on Power Systems or IBM Z mainframes) differs from standard x86 licensing because Oracle charges per processor differently, taking into account core type, processor architecture, and virtualization. Here’s a detailed breakdown:

1. Processor-Based Licensing

Oracle licenses databases using Processor Metrics, which depends on the number of processor cores and a core factor that varies by CPU architecture.

• IBM POWER / AIX:
  • Each POWER processor core has a core factor (e.g., POWER8/POWER9/POWER10 = 0.5 per core for Oracle Database Enterprise Edition).

  • Formula:

    $$\text{Licenses required} = \text{Total cores} \times \text{Core factor}$$
  • Example: 16-core POWER9 server → 16 × 0.5 = 8 processor licenses.
• IBM Z (Mainframe):
  • Oracle uses Virtual Processor Core Factor Table, often lower than x86.
  • Sub-capacity licensing is available using IBM LPAR definitions.

2. Virtualization Impacts

Oracle allows licensing based on physical cores or virtual cores only if virtualization is certified by Oracle.

• AIX / PowerVM:
  • You can license only the cores allocated to LPARs running Oracle.
  • If using shared processor pools, Oracle counts entitled capacity, not physical cores.
• IBM Z / LPAR:
  • Oracle permits sub-capacity licensing using IBM’s PR/SM LPAR definitions.
  • You only pay for the logical cores dedicated to Oracle workloads.

3. Soft Partitioning vs Hard Partitioning

• Soft Partitioning (like some x86 VMware setups) is not recognized by Oracle—they count all physical cores in the system.
• Hard Partitioning (AIX LPARs or IBM Z LPARs) is recognized by Oracle, allowing you to license only the partition running Oracle.

4. Oracle Options and Packs

• Options like Partitioning, RAC, Active Data Guard, Advanced Compression are licensed per processor as well.
• On IBM platforms, this means each licensed core in an LPAR or partition counts toward the option cost.

5. Key Differences vs x86

6. Best Practices for IBM Platforms

1. Use dedicated LPARs for Oracle workloads to minimize licenses.
2. Apply core factors correctly based on Oracle’s current documentation.
3. Avoid using soft-partitioned systems for Oracle to prevent over-licensing.
4. Consider Oracle RAC: license only cores used for RAC nodes in each LPAR.
5. Track usage regularly with Oracle License Management Services.

✅ Summary

• Oracle licensing on IBM platforms favors hard partitioned systems like AIX LPARs or IBM Z LPARs.
• You can often license fewer cores than physical CPUs due to core factors and sub-capacity licensing.
• Proper LPAR and processor allocation can significantly reduce licensing costs for high-end Oracle deployments.