Oracle Approved Hard Partitioning Guide. Cut the license cost framework.

The Oracle Approved Hard Partitioning framework is the load bearing Oracle on premises licensing optimization framework. It anchors the customer's Oracle Database, Oracle Middleware, Oracle E Business Suite, Oracle Hyperion, and Oracle Java license positions against the broader Oracle Hard Partitioning framework, with licensing tied to actual physical processor cores allocated to the Oracle workload rather than to the entire physical server.

This guide sets out the components that drive the model:

• The broader Oracle Hard Partitioning framework
• The broader Oracle Soft Partitioning framework
• The six Oracle Approved Hard Partitioning Technologies
• The Oracle Capped vCPU framework
• The Oracle authorised cloud environment framework
• How to anchor against the Oracle audit framework

Read the related Oracle services practice, the Oracle knowledge hub, the BYOL versus License Included on Azure, the Oracle Database 23ai licensing guide, and the Oracle contract renewal strategy.

The Oracle Hard Partitioning framework

The broader Oracle Hard Partitioning framework is the load bearing Oracle on premises licensing optimization framework. It anchors the customer's Oracle license position against the Oracle Approved Hard Partitioning framework, with the approved configuration tied to actual physical processor cores allocated to the Oracle workload.

The framework typically delivers material commercial leverage at the Oracle Database Enterprise Edition tier on a per Oracle processor basis, by reducing the customer's Oracle Database license footprint against the full physical server count.

The buyer side move is to anchor the Oracle Hard Partitioning configuration against the actual Oracle workload, with the Approved Hard Partitioning Technologies tied to that same workload. Read the related Oracle Database 23ai licensing guide.

The Oracle Soft Partitioning framework

The Oracle Soft Partitioning framework is the Oracle non Approved Partitioning framework. It anchors the customer's Oracle license position against the entire physical server, regardless of the virtual machine or container allocated to the Oracle workload.

Oracle Soft Partitioning typically applies to:

• VMware vSphere ESXi (the customer's VMware framework)
• Microsoft Hyper V
• Red Hat KVM (without Oracle Approved Hard Partitioning configuration)
• Linux Containers

Oracle frequently uses Soft Partitioning to drive material commercial leakage at audit. The buyer side move is to migrate the Soft Partitioning estate onto an Approved Hard Partitioning configuration. Read the related Oracle Soft Partitioning versus Hard Partitioning.

The Oracle Approved Hard Partitioning Technologies framework

The Oracle Approved Hard Partitioning Technologies framework is the load bearing Oracle on premises Hard Partitioning anchor. It segments across six Approved Hard Partitioning Technologies:

1. Oracle Solaris 10 Resource Manager, anchored against the Solaris Containers framework.
2. Oracle Solaris 11 Resource Manager, anchored against the Solaris Zones framework.
3. Oracle VM Server, anchored against the Oracle VM CPU pinning framework.
4. IBM AIX Workload Partitions.
5. IBM PowerVM Logical Partitions (LPARs).
6. HP UX Process Resource Manager.

The buyer side move is to anchor the customer's Approved Hard Partitioning Technology against the actual Oracle workload. Read the related Oracle Approved Hard Partitioning Technologies.

The Oracle Capped vCPU framework

The Oracle Capped vCPU framework is the Oracle Approved Hard Partitioning anchor for Microsoft Azure. It anchors the customer's Oracle license position against Azure constrained vCPU virtual machines, including the E series, D series, F series, and M series Azure VMs that carry vCPU caps.

The buyer side move is to anchor the Oracle Capped vCPU position against the customer's Azure constrained vCPU virtual machine inventory. Read the related BYOL versus License Included on Azure.

The Oracle authorised cloud environment framework

The Oracle authorised cloud environment framework is the Oracle BYOL anchor for hyperscale clouds. It segments across three authorised clouds:

• Microsoft Azure
• Amazon Web Services
• Oracle Cloud Infrastructure

The framework anchors the customer's Oracle Database license position on a two virtual CPU per Oracle processor license basis with hyper threading enabled.

The buyer side move is to anchor the authorised cloud environment against the customer's Azure constrained vCPU virtual machines, the AWS dedicated host estate, and the Oracle Cloud Infrastructure footprint. Read the related Oracle Cloud licensing policy.

The Oracle Hard Partitioning audit framework

The Oracle Hard Partitioning audit framework is the load bearing Hard Partitioning compliance framework. It anchors the customer's Hard Partitioning configuration against the Oracle audit framework, which typically arrives as either an Oracle LMS soft audit or an Oracle LMS contractual audit.

Three buyer side moves anchor the Hard Partitioning audit posture:

1. Document the configuration. Document the Approved Hard Partitioning Technology configuration against the actual Oracle workload.
2. Anchor against deployment. Anchor the Approved Hard Partitioning framework against the customer's Oracle Database deployment.
3. Anchor against the master agreement. Anchor the Hard Partitioning audit posture against the Oracle Master Agreement.

Read the related Oracle audit defense service.

How we engage on Oracle Approved Hard Partitioning

Redress engages on the Oracle Approved Hard Partitioning framework across three engagement models:

1. Oracle Approved Hard Partitioning assessment. Typically anchors against the customer's Oracle Database license position, Hard Partitioning configuration, Soft Partitioning footprint, and Oracle authorised cloud environment.
2. Oracle Approved Hard Partitioning audit defense. Typically anchors against the Oracle LMS audit, the Oracle Master Agreement, and the Oracle Approved Hard Partitioning Technologies in scope.
3. Oracle Vendor Shield. Always on multi vendor advisory across the Oracle estate and the broader publisher portfolio.

Read the related Vendor Shield, the Renewal Program, and the Benchmarking framework.

Redress is independent. Buyer side. Industry Recognized. Five hundred plus enterprise software engagements. $2B+ in client spend under advisory. Eleven vendor practices. One hundred percent buyer side. Read the related About Us page, the management team page, the locations page, and the contact page.