Oracle’s Partitioning Policy is not a legally binding contract, yet Oracle routinely cites it during audits to claim additional licences. CIOs, CTOs, and IT procurement leaders need to understand how to leverage their actual Oracle contract terms to push back against unwarranted licensing demands in virtualised environments.
Oracle’s Partitioning Policy is an internal document that classifies virtualisation technologies into “hard” and “soft” partitioning for licensing purposes. Crucially, Oracle includes a disclaimer in this document stating that it is for educational purposes only and “may not be incorporated into any contract and does not constitute a contract or commitment.” No customer has signed this policy as part of their agreement — it is a guideline, not a binding rule.
This distinction is fundamental. Oracle cannot unilaterally enforce the Partitioning Policy if it contradicts your negotiated contract terms. Oracle also reserves the right to update or modify the policy at any time without notice — another reason it is not embedded in contracts. Your licensing rights and obligations cannot be changed by Oracle posting a new PDF on their website.
The policy provides Oracle’s interpretation of how virtualisation should affect licensing, but it carries no contractual weight. It is Oracle’s “wish list” for how customers should licence in virtualised environments.
Oracle reserves the right to modify the policy at any time without notice. Your contractual rights are fixed at the point of signing; they cannot be altered by a unilateral policy update.
Your Oracle licence agreements (OMA, ordering documents, OLSA) typically do not reference the Partitioning Policy. There is no clause tying your obligations to that document.
In any dispute, the signed contract governs. Courts enforce contracts, not vendor policy documents. Oracle knows this, which is why they prefer to settle disputes quietly rather than test the policy in court.
Understanding this separation between policy and contract is the essential first step in preparing to challenge Oracle’s licensing claims. Read our comprehensive guide to Oracle’s Partitioning Policy for the full technical and commercial context.
For enterprise customers, the authoritative source of licensing requirements is the Oracle Master Agreement (OMA) and any applicable licence definitions in your ordering documents or Oracle’s Licence and Services Agreement (OLSA). These contracts outline what you are legally required to licence. It is worth noting that many enterprises have multiple Oracle agreements accumulated over years of purchases, acquisitions, and renewals. Each agreement may contain slightly different language. Ensure you review all applicable agreements — not just the most recent one — as Oracle will typically apply whichever interpretation maximises their claim:
Your organisation runs Oracle Database on a VMware cluster with 10 hosts, but the Oracle VM only runs on 2 of those hosts. Your OMA states you must licence processors where the software is running. Under your contract: you need to licence 2 hosts (16 cores). Under Oracle’s policy: Oracle claims you need to licence all 10 hosts (80 cores). This represents a 5× overclaim. In this scenario, the contract terms prevail legally — the policy has no contractual authority to expand your licensing obligation beyond the 2 hosts where Oracle is actually installed and running.
Although the policy is not binding, Oracle’s Licence Management Services (LMS) auditors frequently reference it during compliance reviews. You may receive an audit report stating that, because you run Oracle on a virtualisation platform such as VMware or Microsoft Hyper-V (which Oracle considers “soft partitioning”), you must licence an entire cluster or environment.
| Oracle’s Tactic | What They Claim | The Reality |
|---|---|---|
| Full cluster licensing | All hosts in your VMware cluster must be licensed, regardless of where Oracle runs | Your contract requires licensing only where Oracle is installed and/or running |
| vMotion risk | Because VMs could migrate to any host, all hosts must be licensed | Potential mobility is not actual installation; affinity rules and documentation limit scope |
| Soft partitioning rejection | VMware, Hyper-V, KVM are “soft partitioned” and do not limit licence requirements | This classification exists only in the policy document, not in your contract |
| NUP escalation | NUP minimums must be calculated against all hosts in the cluster | NUP minimums apply only to the processors you are contractually required to licence |
Oracle pursues these tactics for three primary reasons. First, applying the broadest interpretation maximises the claimed compliance gap, often worth millions — creating enormous pressure to purchase additional licences or cloud subscriptions. Second, many IT and procurement professionals are not aware that the policy is non-contractual, and Oracle leverages this uncertainty deliberately. The official tone and formatting of the policy document can make it sound authoritative, so an unprepared team may assume it must be followed. Third, Oracle auditors frequently use the policy as a negotiation starting point, expecting pushback — if you do not push back, they achieve a windfall; if you do, they “graciously” offer a compromise that still involves purchasing some licences, thus still generating incremental revenue for Oracle.
“Oracle’s Partitioning Policy is a scarecrow. If every customer simply followed it, Oracle would sell vastly more licences. Oracle publishes it to influence customer behaviour and protect revenue. It works for customers who are unaware of their rights — but it crumbles when you point to the contract.”
A financial services firm received an Oracle LMS audit report claiming a £4.2 million compliance gap based on licensing all 24 hosts in their VMware cluster for Oracle Database Enterprise Edition. Oracle’s audit referenced the Partitioning Policy exclusively. The firm’s independent licensing advisor reviewed the OMA and confirmed the contract defined “Processor” as the processor where Oracle is installed and/or running. By documenting that Oracle ran on only 5 hosts (with DRS affinity rules preventing migration), the firm responded with evidence limiting scope to 5 hosts. After legal correspondence citing the contract language and the policy’s own disclaimer, Oracle reduced the claimed gap to £850,000 — an 80% reduction — which was then negotiated further as part of a broader commercial discussion.
A North American manufacturing enterprise running Oracle E-Business Suite on VMware received an audit notification from Oracle LMS. Anticipating a Partitioning Policy-based claim, the enterprise proactively engaged independent counsel and compiled documentation of their Oracle deployment: Oracle ran on a dedicated 4-host VMware cluster (isolated from the broader 40-host virtualisation estate) with strict affinity rules and no vMotion enabled between the Oracle cluster and other clusters. When Oracle’s initial audit findings attempted to include all 40 hosts, the enterprise responded with configuration evidence and contract language analysis. Oracle’s LMS team withdrew the broader claim within two weeks, and the final compliance assessment was limited to the 4 dedicated hosts — avoiding a $2.3 million overclaim entirely.
When facing Oracle on partitioning issues, preparation and a firm understanding of your agreements are critical. The following strategies have proven effective for enterprises defending their position:
Always redirect the conversation to the terms outlined in your written contract. If Oracle claims you need to licence cores where software is not running, ask them to point to that requirement in your OMA or ordering document. In most cases, they cannot, because it is not there. Frame every response in contract terms: “Our compliance is based on the terms of the Oracle licence agreement we signed, which defines a Processor as the processor on which the programs are installed and/or running.”
Maintain clear, contemporaneous documentation of where Oracle software is installed and running. For virtualised environments, this means records of VMware host affinity rules, cluster configurations, DRS group settings, and any technology used to pin or limit Oracle to specific servers. If you can demonstrate that Oracle only ever ran on specific hosts, your position is materially strengthened. Documentation should include timestamps, change records, and configuration audit trails.
It can be powerful to remind Oracle that their own policy document states it is not contractual. Respond in writing: “Oracle’s Partitioning Policy is noted as a reference guide and is not part of our agreement. Our compliance is based on the terms of the Oracle licence agreement we signed.” Putting this in writing creates a documented record that Oracle must address substantively.
If Oracle is pushing hard, involve your in-house legal team or external counsel with experience in software licensing disputes. Legal correspondence carries more weight than operational pushback. Oracle is less likely to insist on a position they know will not hold up legally, especially if they sense you are willing to challenge them formally. Legal involvement signals seriousness and often causes Oracle to moderate their position.
Do not fill out Oracle audit questionnaires or attestations that assume the Partitioning Policy rules. A question like “How many hosts are in your VMware cluster?” is designed to establish a licensing scope based on the policy, not your contract. Instead, respond on your terms: “We run Oracle on X hosts and have licensed those hosts per our contract.” Never volunteer information that expands your licensing scope beyond contractual requirements.
It is known in the ITAM and SAM community that organisations have successfully challenged Oracle’s broad partitioning claims. There have been cases — including legal actions in the UK and elsewhere — where Oracle’s attempt to enforce the policy was dropped or settled in favour of the customer. Being aware of these precedents can strengthen your negotiation position. Oracle knows that if pushed to legal arbitration, the policy alone is not a reliable foundation for their claim.
Beyond reacting during an audit, CIOs and CTOs should take proactive steps to minimise exposure and strengthen their defensive position. The enterprises that fare best in Oracle audits are those that prepared before the audit letter arrived — not those that scrambled after receiving it:
Ensure that IT operations, solution architects, and procurement staff understand both the Partitioning Policy and its non-binding nature. If everyone understands the technical and legal distinctions, you are less likely to inadvertently concede ground during an audit. Run annual training sessions covering Oracle licensing fundamentals, including the critical difference between policy documents and contractual obligations.
Where practical, contain Oracle software to a limited set of servers or a dedicated cluster. This constrains the scope of any licensing demand, even if Oracle attempted to apply the policy. Do not mix Oracle and non-Oracle workloads across a large virtualisation estate; create a small, isolated cluster for Oracle in VMware so the “blast radius” of any licensing claim is limited to the fewest possible hosts.
Configure VMware DRS affinity rules, host groups, and VM groups to pin Oracle workloads to specific hosts. While Oracle does not recognise these as “hard partitioning,” they serve as powerful evidence that Oracle software was never installed on or available to other hosts in the cluster. Document these configurations with dated screenshots, change management records, and periodic audit reports. This evidence trail is invaluable if Oracle challenges your licensing scope.
In risk management terms, know your exposure. Calculate how much it would cost if Oracle’s policy were applied to your entire virtualised environment. Share this “what-if” scenario with senior management to illustrate why controlling Oracle deployment and maintaining contractual preparedness is essential. It also ensures you have budget contingency plans in case you ever need to settle a dispute.
Keep an eye on Oracle’s official communications and support notes. Although the policy is not contractually binding, Oracle occasionally updates it or issues statements regarding virtualisation. If they change their stance — for example, endorsing a new technology for partitioning — you will want to know. Public statements by Oracle executives or court case outcomes may also influence how far Oracle will pursue claims in your specific situation.
Understanding the policy’s content — even though it is not contractual — helps you anticipate Oracle’s arguments and prepare counterpoints:
Technologies Oracle recognises as hard partitioning include: Oracle VM, Oracle Solaris Zones (Capped), IBM LPAR, physical partitioning (separate physical servers). With these technologies, Oracle agrees you only need to licence the partition’s allocated resources, not the entire physical server. Hard partitioning is the only form Oracle acknowledges as limiting licence scope under the policy.
Technologies Oracle classifies as soft partitioning include: VMware ESXi/vSphere, Microsoft Hyper-V, KVM, Citrix Xen, Docker containers, and most public cloud instances. Under the policy, Oracle claims soft partitioning does not limit licensing — you must licence all physical cores in the server or cluster, regardless of what is allocated to the Oracle VM.
Regardless of how Oracle classifies your virtualisation technology, your contract defines your obligations. If your OMA says “licence where installed and/or running,” that is your legal requirement. The policy’s hard/soft distinction is Oracle’s internal framework, not a contractual term you agreed to. Document where Oracle runs and licence accordingly.
Read our practical guide to Implementing Oracle-Approved Hard Partitioning if you want to satisfy both the contract and the policy for maximum protection.
For organisations that want to eliminate any residual risk, migrating Oracle workloads to Oracle’s own approved hard partitioning technologies (Oracle VM, Oracle Linux KVM, or Oracle Solaris Zones with capped resources) removes the virtualisation debate entirely. However, this carries its own costs: infrastructure migration, operational retraining, and potentially reduced flexibility compared to VMware. The decision should be driven by a cost-benefit analysis comparing the total cost of migration against the risk-adjusted cost of defending your VMware position contractually. In many cases, the contractual defence approach is more cost-effective, particularly for enterprises with well-documented VMware configurations and experienced licensing teams.
Have your legal or IT asset management team review every Oracle licence agreement for any language related to virtualisation, partitioning, or server definitions. Rely on the contract, not Oracle’s website policies, to determine compliance. If your contract is silent on virtualisation, that silence benefits you — there is no contractual basis for Oracle to demand licensing beyond actual usage.
Keep detailed, dated records of Oracle software deployment: network diagrams, VMware cluster configurations, host affinity rules, and logs showing which hosts Oracle runs on. This evidence is invaluable during an audit and can be the difference between a multi-million pound overclaim and a clean bill of compliance.
Establish a standing team of licensing specialists, legal counsel, and infrastructure architects who are trained to handle Oracle audits. Ensure they understand that the Partitioning Policy is not binding and are ready to push back using contractual terms. Rehearse the audit response process annually so the team is prepared when Oracle engages.
Consider bringing in independent Oracle licensing advisors when facing an audit or negotiating a contract. Independent experts can identify where Oracle’s claims overreach, articulate counter-arguments effectively, and provide credibility that strengthens your position. Oracle’s auditors respond differently when they know an experienced independent advisor is involved.
If you foresee heavy virtualisation use (extensive VMware or cloud deployments), consider negotiating explicit terms in writing with Oracle during contract renewal. Even if Oracle resists adding clauses that undermine the policy, any written acknowledgement or specific contract language clarifying your virtualisation rights makes future audits significantly simpler to defend.
No. The Partitioning Policy is explicitly non-contractual. It is a guideline published by Oracle, but it is not part of your licence agreement unless you have somehow incorporated it (which most enterprises have not). Oracle cannot directly enforce it in court as if it were a contract term. The policy itself contains a disclaimer stating it does not constitute a contract or commitment.
Request that the auditor identify the specific clause in your signed agreement that imposes those requirements. If they cannot (and they usually cannot), respond in writing that your organisation complies with the terms of the signed contract. Involve your legal team and, if appropriate, an independent Oracle licensing advisor. Standing firm and demonstrating awareness of your contractual rights typically causes Oracle to moderate their position.
It generally helps you. If the contract is silent on virtualisation, there is no contractual basis for Oracle to demand licensing beyond the environments where Oracle software is actually installed and running. Oracle may argue the policy in an audit, but without a contract clause to support the claim, your defence is strong. The burden of proof falls on Oracle to demonstrate a contractual requirement, not on you to disprove a policy claim.
Oracle cannot terminate your licences for not following a non-contractual policy. They could threaten or attempt to impose penalties in an audit report, but any resolution comes down to either settling commercially or, at worst, legal action. If you are compliant with your contract terms — you have licensed all servers where Oracle is installed and running — Oracle has no legitimate ground to terminate your licence or impose penalties.
Yes. Organisations have successfully pushed back against Oracle’s broad partitioning claims by pointing to contract language. In a publicised UK case, Oracle’s expansive claims regarding VMware were not enforced after the customer stood firm, and the matter was settled in the customer’s favour. Oracle generally prefers to settle quietly rather than create legal precedent that undermines the commercial utility of their Partitioning Policy.
If the opportunity arises (such as during a renewal or new purchase), it is worth pursuing. Oracle typically resists clauses that undermine the policy, but some customers have negotiated cloud-specific terms or virtualisation carve-outs. Even without an explicit clause, the standard contract language (“licence where running”) provides protection. However, an explicit clause naming VMware and confirming that only hosts running Oracle require licensing would make future audits significantly simpler to defend.
The Partitioning Policy primarily addresses on-premises virtualisation technologies. Oracle has separate policies for authorised cloud environments (AWS, Azure, Oracle Cloud Infrastructure), which allow different counting methods such as licensing by virtual CPUs. Those cloud rules are distinct from the on-premises policy. Always refer to the specific cloud licensing policy if you run Oracle in a public cloud, and ensure it does not contradict your contract terms.
Redress Compliance provides independent, vendor-neutral Oracle audit defence — ensuring you respond based on your contractual rights, not Oracle’s policy preferences.
Book a Consultation Oracle Audit Defense Service →