In 2022, Oracle quietly adjusted its support policy in a way that could lock customers into higher costs. Many buyers are now grappling with a gap between what their contracts say and what Oracle's policies claim.
Read our comprehensive guide to Oracle support optimization.
Oracle's Contracts vs. Policies — Why They Differ
Bilateral & Binding
The OMA and ordering documents are negotiated, mutually agreed, and legally binding. If it's not in the signed documents, Oracle cannot enforce it. Contracts are king.
Unilateral & Changeable
Oracle's Technical Support Policies are drafted by Oracle alone and can change without customer consent. They're standard operating procedures — not negotiated rights.
Contracts Govern Rights
Your OMA and ordering documents govern your rights and obligations. Policies do not override a contract.
Policies Apply Only as Agreed
Oracle's policies apply generally, but only to the extent referenced in your contract. New restrictions not in your contract are on shaky ground.
If Contract and Policy Clash
Your contract wins. Oracle may claim a policy gives them certain rights, but if your contract doesn't say that, you have strong grounds to challenge.
Oracle Master Agreement (OMA) Structure
Each Order = Separate Contract
Every ordering document constitutes a separate mini-contract. Orders are typically independent of each other unless explicitly linked.
Perpetual vs. Subscription Orders
On-premises perpetual licenses and cloud subscriptions are different orders, often under different addenda. These are separate transactions.
Support Tied to Each Order
Support applies to specific licenses in that order. It doesn't automatically extend to or depend on any other order.
No Automatic Bundling
Oracle can't merge separate orders into one giant obligation without it being spelled out. The OMA's structure gives buyers modular control.
How It Worked Before 2022
Separate Worlds
On-premises licenses and cloud subscriptions didn't intersect. You could decide the fate of each independently.
Dropping Support Was Feasible
Customers regularly dropped support on unused licenses to save money — without impacting other products or services.
Perpetual Means Perpetual
Even without support, your perpetual license remained yours. You weren't forced to cancel other services.
Buyer Leverage
This separation gave buyers leverage. You could threaten to cancel unnecessary support to negotiate better pricing — and Oracle had no contractual way to stop you.
Oracle's 2022 Support Policy Change
Forced Bundling of Support
Under "Matching Service Levels," all licenses in a license set must be on the same support status. You can't have a supported cloud subscription while letting on-prem support lapse for the same product.
Pay or Terminate
Oracle's message: if you transition to subscription but retain perpetual licenses, you must either continue paying support on those old licenses or relinquish them entirely.
Unilateral and Non-Contractual
This change was not something customers negotiated or agreed to individually. Many only found out when Oracle's renewal team told them they "weren't allowed" to cancel certain support.
Not Automatically Enforceable
This is Oracle's interpretation. If your contracts were signed before this change (or don't mention it), Oracle can't simply mandate compliance without challenge.
Legal Basis for Pushback
"Show Me Where It Says That"
Your strongest defense. Ask Oracle to point to the exact contract clause. In most cases, it isn't there. Your OMA and order forms likely don't mention bundling perpetual and cloud support.
Contractual Separation
Many OMAs explicitly state each order is a separate agreement. Oracle's retroactive grouping of different orders has no contractual merit.
Policies ≠ Contractual Terms
Changes to policies that materially alter your rights or costs may not be enforceable unless explicitly agreed to. Oracle can't use a generic policy reference to impose huge new restrictions.
No Retroactive Unification
Pushing disparate orders into one "license set" after the fact could be seen as contract modification without consideration or consent.
Contract Law Basics
Ambiguities between a policy and a signed agreement are resolved in favor of the signed agreement. The four corners of the contract contain the agreed terms.
Negotiation Strategies for Buyers
Explicit Order Separation Clause
Insist on language that each order's support is independent — "with no impact on Customer's other orders or licenses."
Define "License Set" Your Way
Redefine the term to mean only licenses on the same ordering document. Explicitly exclude grouping of cloud and on-premises licenses.
Ensure Independent Renewals
Negotiate the right to renew support product-by-product or order-by-order at your sole discretion.
Protect the Right to Drop Support
Add clauses that you can cancel support for any perpetual license without forfeiting the license or affecting other services.
Push Back on Policy References
Negotiate that contract terms govern in any conflict with policies, and material policy changes require mutual written agreement.
Use New Deals as Leverage
Condition signing on these protective terms. Oracle's sales reps will often get approvals for exceptions to close large deals.
Document Oracle's Promises
Never accept oral assurances. Get every important promise in writing — in the contract, an amendment, or an official Oracle document.
Example Scenarios — How Buyers Protect Themselves
Migrating to Cloud, Dropping Legacy Support
An enterprise migrated from Oracle E-Business Suite on-premises to Oracle ERP Cloud. They planned to drop support on old perpetual licenses to save hundreds of thousands per year. Oracle protested, citing the 2022 policy.
The customer's response: "Show us where our contract says that." Their original license order and cloud subscription were separate with no linking clause.
Negotiating Cloud Contract Language Upfront
A company negotiating a new Oracle Cloud deal added language explicitly stating that entering the cloud subscription would have no impact on existing on-premises licenses or support. Oracle initially tried to remove the clause; the customer insisted it was a deal-breaker.
Two years later, when the customer dropped support on old database licenses, Oracle's support team tried to object.
Audit Pushback with Contract in Hand
During a license audit, Oracle's auditors claimed that having an active Java subscription while letting WebLogic support lapse was non-compliant under the support policy. The customer's legal team replied with a detailed letter citing the specific ordering documents.
Oracle Contract Readiness Checklist
FAQs
Need Help Defending Your Oracle Contract Rights?
Redress Compliance provides independent Oracle licensing advisory — from audit defense and support optimization to contract negotiation and ULA certification.