Can I Use Oracle’s Virtualization or Containers to Reduce Licensing Costs for Middleware?

Can I Use Oracle’s Virtualization or Containers to Reduce Licensing Costs for Middleware

Managing licensing costs is crucial for any organization using Oracle middleware. Oracle’s licensing rules are stringent, particularly around virtualization and containerization. Understanding how Oracle treats these technologies can significantly impact your licensing spend. In some cases,

Oracle-approved virtualization technologies can help reduce licensing costs substantially.

Here’s a thorough breakdown of how Oracle’s virtualization and containerization licensing works and how you can leverage certain technologies to manage these costs effectively.

Read Oracle middleware FAQs.

Oracle’s Licensing Approach to Virtualization

Oracle differentiates between two main types of partitioning:

• Soft Partitioning:
  Technologies such as VMware vSphere, Microsoft Hyper-V, and Docker/Kubernetes fall into this category. Oracle does not recognize soft partitioning methods for license containment. Suppose Oracle software runs on a host or cluster using these technologies. In that case, Oracle licensing requires you to license all physical cores that the software could potentially access, regardless of actual usage.
• Hard Partitioning:
  Oracle recognizes specific technologies, such as hard partitioning, which limits license requirements. If Oracle middleware runs in environments using these approved technologies, you can license only the cores specifically assigned to Oracle workloads.

Using approved hard partitioning technologies is crucial to effectively managing Oracle middleware licensing costs.

Approved Oracle Hard Partitioning Technologies

Below are the virtualization technologies Oracle officially recognizes as hard partitioning:

1. Oracle VM Server (OVM)

Oracle VM Server (OVM) is Oracle’s virtualization platform. It is one of the most common solutions organizations use for hard partitioning to limit Oracle licensing.

How it works:

• Create virtual machines (VMs) and explicitly pin virtual CPUs (vCPUs) to physical cores.
• Oracle licensing recognizes these pinned cores as the only cores needing licenses.
• Any Oracle middleware installed on the VM only requires licensing the pinned cores.

Example:

• You have a 32-core physical server.
• You deploy Oracle WebLogic on an Oracle VM with 8 pinned cores.
• You only license the eight pinned cores, significantly reducing your licensing requirement.

Important considerations:

• Pinning must follow Oracle’s guidelines explicitly.
• Keep thorough documentation showing the pinned configuration.
• Changes to core allocation must be immediately updated in licensing.

2. Oracle Linux KVM with Hard Partitioning

Oracle Linux’s Kernel-based Virtual Machine (KVM) implementation can also qualify as hard partitioning when used with specific Oracle-approved tools (e.g., Oracle Linux Virtualization Manager with proper cgroups and CPU affinity settings).

How it works:

• You create KVM guests with CPUs explicitly pinned to host cores.
• Oracle treats these pinned cores as the licensing boundary.
• Requires Oracle Linux and Oracle’s virtualization management tools.

Example:

• Deploy Oracle SOA Suite on Oracle Linux KVM pinned to 4 specific cores out of a 24-core host.
• Licensing only applies to those four pinned cores.

Best practices:

• Regularly audit the configuration.
• Document CPU affinity settings.
• Ensure no drift or movement between cores.

3. IBM PowerVM Logical Partitioning (LPAR)

On IBM Power Systems, Oracle recognizes static Logical Partitioning (LPAR) as hard partitioning.

How it works:

• You configure static LPAR partitions with dedicated cores for each workload.
• Oracle licenses only the cores explicitly dedicated to Oracle middleware workloads.

Example:

• IBM Power server has 32 cores total.
• Assign 8 cores via LPAR dedicated to Oracle WebLogic.
• Licensing covers only these eight cores.

4. Solaris Zones (Capped Zones)

Oracle also recognizes Solaris Zones as valid hard partitions only if configured as capped zones.

How it works:

• Set CPU caps and pin zones explicitly to specific cores.
• Oracle middleware licensing applies only to the capped CPU resources.

Example:

• Solaris server with 16 cores total.
• A Solaris-capped zone assigned explicitly to 4 cores runs Oracle middleware.
• Licensing applies only to these four cores.

Container Technologies (Docker, Kubernetes) and Oracle Licensing

Docker and Kubernetes are popular for deploying middleware workloads. However, Oracle considers container technologies soft partitioning unless explicitly combined with approved underlying hard partitioning methods.

Key points:

• Running Oracle middleware in Docker containers on a host with 32 cores requires licensing all 32.
• CPU limits in Docker or Kubernetes alone do not reduce licensing obligations.
• Only approved hard partitioning methods at the hypervisor or OS level can limit licensing.

Best practices:

• Run containers over approved hard-partitioned hosts (OVM, Oracle Linux KVM).
• Document container-to-core mappings clearly if using Oracle-approved methods underneath.

Oracle Cloud Infrastructure (OCI) and Licensing

Oracle Cloud Infrastructure (OCI) provides a built-in, license-friendly environment for Oracle middleware, significantly simplifying licensing:

How it works:

• OCI uses OCPUs (Oracle CPUs), each typically equivalent to one physical core.
• Oracle explicitly allows sub-capacity licensing on OCI instances.
• Choose OCI shapes that match your existing license entitlements (Bring Your Own License, or BYOL).

Example:

• OCI VM instance configured with 2 OCPUs.
• Requires licensing equivalent to those 2 cores only (often just 1 Processor license if hyper-threaded).

Best practice:

• Move Oracle middleware workloads to OCI to leverage precise licensing containment.
• Document and match licenses to OCI OCPU configuration.

Real-World Example of Licensing Savings with Oracle VM

To illustrate clearly how substantial licensing savings can be achieved:

• Scenario: You have a 16-core physical Intel server.
• If you use VMware (soft partitioning) and deploy Oracle WebLogic even with just 4 vCPUs, you must license all 16 cores.
  • Cost example:
    • WebLogic EE (approx. $25,000 per processor license):
    • 16 cores × 0.5 factor = 8 licenses needed.
    • Cost: 8 × $25,000 = $200,000.
• If using Oracle VM with pinned cores, same 4-core workload:
  • Only license the pinned 4 cores:
  • 4 cores × 0.5 factor = 2 licenses.
  • Cost: 2 × $25,000 = $50,000.

This represents a 75% licensing cost reduction, highlighting why many Oracle customers adopt Oracle-approved virtualization strategies.

Compliance Considerations and Documentation

To maintain compliance and effectively leverage Oracle’s approved virtualization:

• Strictly adhere to Oracle’s guidelines for each approved technology.
• Maintain clear, accurate documentation of configurations and mappings.
• Regularly audit and verify that your configurations have not drifted or changed inadvertently.
• Provide clear evidence in case of Oracle licensing audits demonstrating your use of approved hard partitioning.

Read if Oracle SOA Suite includes WebLogic Server or other prerequisites.

Licensing Risks and Pitfalls to Avoid

Common pitfalls in virtualization licensing include:

• Soft partitioning methods (VMware, Hyper-V) are used to limit licensing. Oracle does not recognize these as valid.
• Containers on non-hard-partitioned hosts: Docker alone is insufficient to limit licenses.
• Drift in hard partitioning: Changes in pinned cores or partitions without immediate licensing updates can cause compliance issues.

Summary of Oracle Virtualization Licensing Options

Conclusion and Best Practices

Oracle’s approved virtualization technologies (Oracle VM, Oracle Linux KVM, IBM LPAR, Solaris Zones, OCI) can significantly reduce middleware licensing costs. Organizations should prioritize these technologies for Oracle middleware deployments and rigorously maintain documentation to ensure ongoing compliance and optimal licensing costs.

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

Please enable JavaScript in your browser to complete this form.

Name *

Email *

Company

Message *

Submit