Oracle hard partitioning. Cut cores, keep the savings at audit.

Oracle accepts a short list of hard partitioning technologies. Configured and evidenced exactly as the policy describes, they cut Database license cost by 30 to 60 percent and hold at audit.

What does Oracle approved hard partitioning actually permit?

Hard partitioning lets you license Oracle Database to the physical cores actually allocated to the Oracle workload instead of the full server, and Oracle recognizes only the technologies named in its partitioning policy document. Everything else counts as soft partitioning and licenses the whole machine.

The policy is not part of your contract. It is a published Oracle position paper, which cuts both ways: it is not binding on you, but Oracle audit teams apply it without exception.

Which technologies does Oracle accept?

The accepted list is short and specific. The most used entries in current estates are:

• Oracle Linux KVM with hard partitioning configuration. CPU pinning set per the Oracle Linux documentation, evidenced with config exports.
• Solaris Capped Zones. Capped zones only; uncapped zones license the full server.
• IBM LPAR. Dedicated or capped shared processor pools on Power systems.
• Oracle VM Server (legacy). Pinned vCPU configurations on the deprecated OVM stack.
• Capped vCPU in authorized clouds. A separate cloud policy governs AWS, Azure, and OCI counting.

What never qualifies?

VMware vSphere, Microsoft Hyper V, and Nutanix AHV never qualify, regardless of pinning, affinity rules, or DRS host groups. Oracle's position licenses every physical host where the workload could run, and with vSphere clusters that can mean the entire estate.

How do you implement a capped configuration that survives an audit?

An implementation survives audit when the capping mechanism, the core count, and the evidence trail all match the policy text. The configuration alone is not enough; you need timestamped proof it was in place for the whole license period.

The evidence package that closes audit questions

Keep configuration exports, change tickets, and quarterly screenshots for every capped host. In the audits we defended, the estates that produced dated evidence within two weeks closed partitioning questions without findings.

Where the common advice on hard partitioning is wrong

The standard advice is to avoid hard partitioning because Oracle audits it aggressively. We disagree. In roughly 15 of 20 capped implementations Fredrik Filipsson reviewed in 2024 to 2025, the configuration held at audit and the customer kept savings of 30 to 60 percent on Enterprise Edition licensing. The estates that lost were the ones that pinned CPUs informally and never matched the policy text. The buyer side move is to implement exactly what the policy describes, document it quarterly, and treat the policy PDF as the audit script it is.

Hard partitioning is not a loophole. It is Oracle's own policy, applied precisely. The customers who lose are the ones who improvise.

When does hard partitioning beat the alternatives?

Hard partitioning wins when a large physical estate runs a small, stable Oracle footprint; consolidation, BYOL to OCI, or a move to Standard Edition 2 can beat it when the footprint is shrinking. Model all three before committing engineering time.

1. Stable workload, big server: cap the cores and cut the Enterprise Edition count.
2. Shrinking workload: consolidate first; capping a dying estate wastes effort.
3. Cloud bound workload: use the cloud counting policy and skip on premise capping.

The renewal angle most teams miss

A capped configuration changes your support baseline as well as your license need. Reducing licensed cores ahead of a renewal resets the support stream before the uplift compounds, which is where the multi year money is. See the Oracle support cost reduction guide for the sequencing.

What to do next

1. Inventory every host running Oracle and the hypervisor under it.
2. Pull the current Oracle partitioning policy PDF and map each platform to hard, soft, or cloud treatment.
3. Quantify the gap between licensed cores and policy compliant countable cores.
4. Implement capping per the policy text on qualifying platforms, with change tickets.
5. Build the quarterly evidence pack: config exports, screenshots, timestamps.
6. Re baseline support costs before the next renewal conversation.
7. Have the position reviewed independently before Oracle ever asks.

Start with the Oracle advisory practice or the Oracle knowledge hub. The Oracle partitioning policy guide covers the policy document clause by clause, and Vendor Shield keeps the position reviewed year round.

Frequently asked questions

What is the difference between Oracle hard and soft partitioning?

Hard partitioning physically caps the cores available to Oracle and licenses only those cores. Soft partitioning, which includes VMware and Hyper V in any configuration, does not limit license scope, so the full server or cluster must be licensed.

Does VMware CPU pinning count as hard partitioning?

No. Oracle treats every VMware configuration as soft partitioning, including pinning and host affinity rules. Oracle expects every host where the workload could run to be licensed, which in a vSphere cluster can mean all of them.

Which technologies does Oracle approve for hard partitioning?

The policy names Oracle Linux KVM with capped configuration, Solaris Capped Zones, IBM LPAR with capped pools, legacy Oracle VM Server, and capped vCPU counting in authorized clouds under the separate cloud policy.

How much can hard partitioning save on Oracle licensing?

In the 2024 to 2025 positions we reviewed, correctly implemented capping cut Oracle Database Enterprise Edition license requirements by 30 to 60 percent against full server licensing, and the savings held through audit where evidence was kept.

Is the Oracle partitioning policy legally binding?

The policy is a published Oracle position paper, not a contract term. In practice Oracle audit teams apply it strictly, so the pragmatic move is to implement to its letter and document the configuration continuously.