Hundreds of Oracle customers run on third party support. The route is legal when run correctly. The buyer side view of the Rimini Street rulings, the intellectual property guardrails, the contract conditions, and the questions in house counsel should answer before any switch.
Oracle third party support is legal. Hundreds of large Oracle customers run on third party support today. Banks, retailers, manufacturers, public sector agencies, and global brands all use the route. The legality is not in question. The intellectual property guardrails matter.
The 2016 and 2018 Rimini Street rulings drew a clear line. The customer retains the right to use the licensed Oracle software under the existing license agreement. The third party support provider may maintain the running estate. The provider may not copy Oracle intellectual property beyond what the license permits.
This article reads the legal landscape from the buyer side. Pair it with the Oracle third party support comparison, the support renewal guide, the audit defense framework, and the Oracle Hub.
Oracle revisits the question through every renewal cycle. The Oracle sales motion frames third party support as risky, unsupported, or non compliant. The framing is a commercial tactic, not a legal opinion. The Oracle license agreement, the case law, and the operating practice of hundreds of large customers all support the legality of the route.
The Rimini Street litigation against Oracle ran from 2010 to 2018. The case produced two material rulings that set the boundary for third party support of Oracle products. Both rulings affirmed the legality of the third party support business model. Both rulings drew a clear line on the handling of Oracle intellectual property.
| Year | Court | Ruling | Buyer side meaning |
|---|---|---|---|
| 2014 | US District Court | Third party support is a legitimate business | The customer can engage a third party support provider |
| 2016 | Ninth Circuit | Copying patches into a generic environment infringes | The provider must use the customer environment for support work |
| 2018 | US Supreme Court | Damages calculation reduced | The boundary applies, but the third party support model continues |
| 2021 to 2023 | Subsequent enforcement | Continued enforcement of the IP boundary | The model continues with sharper IP guardrails |
The US Supreme Court reduced the damages calculation against Rimini Street in 2018. The ruling did not invalidate the third party support model. Third party support remains legal. The model adjusted to use the customer environment for support work rather than provider hosted libraries.
The intellectual property boundary sits on three principles. The customer may use the Oracle software under the existing license. The third party support provider may maintain the customer environment under that license. The provider may not copy Oracle materials beyond what the license permits.
| Activity | Inside the IP boundary | Outside the IP boundary |
|---|---|---|
| Running existing Oracle software | Inside the boundary | n/a |
| Provider support on customer environment | Inside the boundary | n/a |
| Applying a security fix the provider authored | Inside the boundary | n/a |
| Applying a new Oracle patch released after support lapsed | n/a | Outside the boundary |
| Upgrading to a new Oracle major version | n/a | Outside the boundary |
The Oracle license agreement (OLSA, OMA, MSA) and the Software Update License and Support order (SULS) carry the conditions that govern the support relationship. The customer should read the active contract before switching. Most clauses are favorable to the third party support route. A small number require attention.
The Oracle reinstatement fee equals the lapsed support payments plus a 150 percent penalty plus the renewal at list price. The fee is contractual. Customers who return to Oracle support after a lapse pay this fee. The fee should not deter the move, but it should appear in the business case.
The buyer side workflow runs the third party support evaluation through internal counsel before signature. The five questions below sit at the core of the legal review. Each one has a settled answer in the case law and the contract.
The switching workflow takes six to nine months on a typical estate. The work runs three streams in parallel. Compliance hygiene, internal alignment, and provider selection move together and converge on the support anniversary.
The eight step checklist below moves the third party support evaluation from rumor to documented decision. Open it nine months before the Oracle support anniversary. The earlier the work starts, the cleaner the switch.
Yes. The 2014 to 2018 Rimini Street litigation settled the legality of the third party support business model. Customers retain the right to use Oracle software under the existing license agreement. Third party support providers may maintain the running customer estate. The case law also defined the intellectual property boundary that providers must respect.
The rulings affirmed that third party support is a legitimate business and that customers can engage a third party provider. The rulings also defined the intellectual property boundary. Providers may not copy Oracle materials into a generic environment beyond what the license permits. The model adjusted to use the customer environment for support work and continues today.
Yes, but BYOL to Oracle Cloud requires active Oracle support on the relevant licenses. Most customers segment the estate. Database servers remain on perpetual licenses with third party support, while a smaller Oracle Cloud footprint runs with active Oracle support. The segmentation preserves the savings on the bulk of the estate.
The Oracle reinstatement fee applies. The fee equals the lapsed support payments plus a 150 percent penalty plus the renewal at list price. The fee is contractual and is documented in the order. The cost should appear in the business case for switching but should not deter the move on most estates given the multi year savings.
No, the perpetual license remains in effect. Oracle perpetual licenses are not contingent on continuing to buy Oracle Premier Support. The customer can drop support at the anniversary without losing the license. The audit clause remains in effect and the customer must continue to comply with the license terms.
Nine months before the Oracle support anniversary. The audit and reconciliation work runs in months one to four. Provider selection runs in months three to six. Internal sign off runs in months five to eight. The non renewal notice files at month nine. The switch executes on the anniversary date.
Redress runs the Oracle third party support evaluation as a 12 to 16 week engagement. The work pulls the Oracle license footprint, reconciles deployment against entitlement, models the multi year savings, scores two or three providers, and walks the internal legal review. The deliverable is a documented decision, a transition plan, and a 24 month watch list.
Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.
A buyer side framework for the next Oracle support renewal, ULA decision, or third party support evaluation. License hygiene checklists, reinstatement math, IP boundary tests, and the provider scoring rubric.
Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for enterprise customers running Oracle Database, middleware, applications, and Java at scale.
Open the white paper in your browser. Corporate email only.
Open the Paper →We walked the legal review through the Rimini Street rulings, reconciled the Oracle Database entitlement against deployment, modeled a five year third party support savings of forty one million dollars, scored three providers, kept Oracle Cloud BYOL on standing support, and signed the non renewal notice on the anniversary.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
Third party support market shifts, reinstatement penalty patterns, BYOL to Oracle Cloud rule changes, audit posture signals, and the wider Oracle commercial trends across every renewal cycle.
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.
