The Oracle partitioning policy decides whether a four core VM costs you one license or a hundred. Soft partitioning, hard partitioning, and the LMS rule book sit at the heart of every Oracle audit that crosses VMware. This is the buyer side reference.
Oracle splits the world into two virtualization buckets. Hard partitioning lets you license a subset of cores. Soft partitioning, in Oracle eyes, does not. Everything VMware does sits in the second bucket by default, which is why VMware estates carry the biggest Oracle audit exposure across any infrastructure category.
The partitioning policy is not in the contract. It is a public LMS document that Oracle updates without notice. The buyer side discipline is to anchor the contract to a fixed partitioning position, not to the floating policy, before the audit lands.
Pair this article with the Oracle knowledge hub, the Oracle advisory practice, the ULA decision framework, the Database 23ai licensing guide, the Java audit guide, and the Vendor Shield subscription before the next Oracle audit notice arrives.
The Oracle partitioning policy is a two page LMS document hosted on the Oracle website. It defines which virtualization technologies are recognized as hard partitioning and which are recognized as soft. The list is updated unilaterally by Oracle.
Audit math against the soft partitioning rule produces the biggest single Oracle exposure category. A modest VMware estate can carry five to ten million US dollars of nominal license liability under the strict reading. The buyer side discipline is to neutralize the rule, not to argue it.
Oracle splits virtualization into two buckets. The hard partitioning bucket is a finite list of technologies. The soft partitioning bucket is everything else. The list is short and the consequences of being outside it are significant.
| Technology | Oracle category | Sub host licensing | Audit risk |
|---|---|---|---|
| VMware vSphere | Soft | Not recognized | High |
| Microsoft Hyper V | Soft | Not recognized | High |
| KVM and Red Hat OpenShift | Soft | Not recognized | High |
| Nutanix AHV | Soft | Not recognized | High |
| Oracle VM Server (Xen) | Hard (with bound CPU) | Recognized | Low |
| Solaris Zones (capped) | Hard | Recognized | Low |
| IBM Power LPAR (capped) | Hard | Recognized | Low |
| HP nPars | Hard | Recognized | Low |
VMware sits at the center of every Oracle partitioning conversation. The default LMS reading licenses every physical core on every host in the vMotion cluster, regardless of which VM Oracle Database actually runs on.
| Mitigation | How it works | Effort |
|---|---|---|
| Physical Oracle cluster | Carve a dedicated cluster with no shared hosts | Low |
| Contract addendum | Written agreement binding a specific partitioning interpretation | High |
| Migrate to OCI or approved cloud | Move to a hyperscaler using the Authorized Cloud Environment metric | Medium |
The Authorized Cloud Environment policy covers AWS, Azure, and Oracle Cloud Infrastructure. The metric converts vCPU to license at one to two with hyper threading on, and at one to one with hyper threading off. Google Cloud sits outside the approved list and runs under standard host based rules.
Oracle has signed partitioning addendums with hundreds of enterprises since 2015. The addendum typically binds the customer to a specific partitioning interpretation that recognizes VMware DRS rules or named host clusters as a licensable boundary.
The lever is negotiation timing. Oracle agrees to addendums at contract signing, at ULA exit, and at large net new spend events. Outside those windows the answer is usually no.
LMS audits open with three common triggers. The buyer side discipline is to know which trigger is in play, since the audit scope, timeline, and settlement leverage shift with it.
The standard audit pack runs ninety to one hundred and twenty days. LMS issues a data collection script, the customer runs it, and the results enter a compliance review. The review identifies the gap. The gap converts to a remediation quote at list price.
The Oracle partitioning rule is the single most expensive sentence in any Oracle audit. A four core VM on a sixteen host VMware cluster equals a hundred and twenty eight licensable cores under the strict reading. Without a contract addendum, that math holds.
The buyer side controls cluster into four categories. The most effective controls are written into the contract before the audit lands. The reactive controls work but cost more.
| Control | Category | Where it sits | Effectiveness |
|---|---|---|---|
| Partitioning addendum | Contractual | Master agreement | High |
| Dedicated Oracle cluster | Architectural | Infrastructure | High |
| Affinity rules and DRS lock | Operational | vCenter policy | Medium |
| BYOL on OCI or AWS | Cloud move | Workload migration | High |
| Third party support exit | Commercial | Renewal | Medium |
| Active LMS data hygiene | Defensive | SAM tool output | Medium |
The seven step checklist below is the buyer side starting position for any Oracle partitioning engagement.
The policy is not part of the standard Oracle Master Agreement. It is a guideline that Oracle treats as binding and that customers can challenge. Audit settlements turn on the contract language. Where the OMA references the policy by name, Oracle has a stronger position. Where it does not, the customer has room to negotiate the interpretation.
DRS affinity reduces operational risk but does not eliminate audit risk. Oracle LMS does not accept VMware affinity as a licensing boundary. The technical control still has value because it limits the practical scope of where Oracle workloads actually run, but the contractual control is the lever that actually stops the audit math.
The metric converts vCPU to license at a two to one ratio with hyper threading enabled, and at one to one without. The metric applies on OCI, AWS, and Azure for Oracle Database, Middleware, and Java workloads. The result is usually a meaningful reduction in license count compared to the on premise host based rule.
It changes the audit math, but it does not eliminate audit risk. Oracle audits run on metric compliance regardless of platform. The OCI BYOL discipline is to size the BYOL subscription correctly, to track active vCPU through the cloud console, and to reconcile monthly. The audit still happens, but the exposure profile is materially lower.
Yes, but only at a contract event. Oracle signs partitioning addendums at master agreement signing, ULA exit, large net new orders, and occasionally at renewal. The addendum language is custom and the negotiation runs in parallel with the commercial deal. An independent advisor brings the addendum templates and the comparable language from prior signed agreements.
Redress runs Oracle partitioning engagements inside the Vendor Shield subscription and the Renewal Program. The work covers the policy review, the architectural inventory, the audit exposure quantification, the addendum target language, and the negotiation sequence. Always buyer side, never Oracle paid.
Redress runs Oracle partitioning engagements inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The Oracle commercial leadership sits with the founders.
Read the related benchmarking framework, about us, locations, and contact pages.
A buyer side reference on the ULA certification math, the partitioning policy interpretation, the audit defense sequence, and the OCI BYOL conversion path. Built from hundreds of Oracle engagements.
Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying Oracle estates. No Oracle influence. No sales kickback.
Open the white paper in your browser. Corporate email only.
Open the Paper →The Oracle partitioning rule is the single most expensive sentence in any Oracle audit. A four core VM on a sixteen host VMware cluster equals a hundred and twenty eight licensable cores under the strict reading. Without a contract addendum, that math holds.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Partitioning addendums signed, ULA exit patterns, Java audit signals, OCI BYOL conversion math, and the wider Oracle commercial leverage signals across every renewal we run.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
