Background: Why Oracle Sued Rimini Street
Oracle, one of the world's largest enterprise software vendors, generates substantial revenue from annual support contracts — typically charging approximately 22% of licence value per year. Rimini Street emerged as a third-party support provider promising Oracle customers equivalent maintenance at roughly 50% lower cost, directly threatening this revenue stream.
In 2010, Oracle filed a lawsuit (the "Rimini I" case) accusing Rimini Street of copyright infringement and unauthorised use of Oracle's software to deliver these services. Oracle alleged that Rimini copied Oracle software code and updates beyond what customer licences permitted, effectively using Oracle's intellectual property to serve multiple clients simultaneously.
Rimini Street countered that it only used Oracle's materials within the rights of customers' licences and that it had already adjusted any processes Oracle found problematic. This conflict set the stage for a high-stakes legal showdown between software IP rights and customers' desire for cheaper, more flexible support.
For a comprehensive assessment of whether third-party support is right for your organisation, see our guide: Is Oracle Third-Party Support Legal?
The Oracle vs Rimini Street case was never really about one provider — it was about whether Oracle could maintain its monopoly on support for its own products. The outcome has permanently changed the leverage equation between Oracle and its customers. Understanding this case is essential for any CIO evaluating their Oracle support strategy.
Timeline of Key Events in the Legal Saga
Oracle initiates suit alleging massive intellectual property theft by Rimini Street in its third-party support activities. The case is filed in the U.S. District Court in Las Vegas, Nevada.
Rimini Street files for a declaratory judgment that its revised, post-2014 support processes no longer infringe Oracle's rights. Oracle countersues, claiming continued violations. Rimini has by this point substantially restructured how it delivers support.
A Las Vegas jury finds Rimini Street liable for copyright infringement and awards Oracle approximately $50 million in damages, plus additional sums for other claims and legal fees (totalling over $100 million). A permanent injunction is issued to prevent Rimini from repeating infringing acts.
The Ninth Circuit upholds the core finding of copyright infringement but reduces some damages. The U.S. Supreme Court limits Oracle's ability to recover certain legal fees. Crucially, 23 of Oracle's 24 original claims are overturned or dismissed, with the remaining infringement deemed "innocent" (unintentional). The permanent injunction remains in effect.
Oracle accuses Rimini of violating the injunction. A court finds Rimini in contempt on several technical points and orders a minor fine of approximately $630,000. Five other alleged violations are rejected, reflecting that many of Rimini's practices were within legal bounds.
A court issues a second injunction tightening restrictions on how Rimini delivers Oracle support (including banning certain automation tools) and compels Rimini Street to issue a public "corrective statement" about past marketing claims.
Oracle and Rimini Street reach a confidential settlement concluding all litigation. Key terms: Oracle returns $37.8 million to Rimini Street, and Rimini agrees to wind down PeopleSoft support by 2028. Both sides drop remaining claims. Neither admits wrongdoing.
For context on Oracle's broader history of licensing disputes, see our analysis of the Oracle vs Mars Lawsuit — another landmark case that exposed Oracle's aggressive audit and licensing practices.
Courtroom Outcomes: What Was Decided
Intellectual Property and Licensing
The courts confirmed that Oracle's software licences and intellectual property rights are enforceable — third-party providers cannot copy or distribute Oracle's software or updates beyond what a customer's licence allows. Rimini Street's early practices of cloning environments and distributing Oracle updates across multiple clients were found to violate copyright law.
Validation of Revised Third-Party Support Model
Critically, through appeals and the Rimini II proceedings, the legal process also validated much of Rimini Street's revised support model. By 2014, Rimini had altered its methods — working exclusively within each client's licensed software environment and no longer reusing Oracle code across customers. The courts recognised these changes: nearly all Oracle claims beyond the early infractions were dismissed. The final judgments characterised the remaining infringement as "innocent," suggesting no willful misconduct once processes were adjusted.
Injunctions as Industry Guidelines
The permanent injunctions now effectively serve as operating guidelines for the entire third-party support industry:
| Injunction Requirement | What It Means in Practice | Impact on the Industry |
|---|---|---|
| Work only with legitimately licensed customers | Providers must verify that each customer holds valid Oracle licences for the software being supported | Ensures third-party support is a complement to — not a replacement for — proper software licensing |
| No unauthorised copying of source code | Providers cannot create generic development environments populated with Oracle software to service multiple customers; each client's work must stay isolated | Established the "single-customer environment" model as the legal standard |
| No cross-client distribution of Oracle updates | Third-party providers can develop their own fixes, but cannot package and distribute Oracle's original patches broadly | Drew a clear line between proprietary Oracle patches and independently developed workarounds |
| Truthful marketing | Providers must not misrepresent their services or Oracle's offerings in marketing materials | Raised the standard for transparency in how third-party support is marketed to enterprises |
These outcomes strike a balance: Oracle's IP rights are protected, but a clear pathway remains open for third-party support firms to operate legally. The legal battle drew an explicit line between what constitutes "legal third-party support" and what crosses into infringement — providing CIOs with the clarity they need to make informed decisions.
Need independent advice on transitioning to third-party Oracle support?
Third-Party Support Advisory →Impact on Enterprise Customers and Vendors
Third-Party Support Confirmed as a Legal Option
For CIOs and sourcing professionals, the most important takeaway is that utilising third-party support for Oracle software is a legally permissible option. Despite 15 years of litigation, the outcome confirms that customers have a choice beyond Oracle's own support — provided the third-party provider respects software licence terms. For a deeper legal analysis, see our guide: Is Oracle Third-Party Support Legal?
Cost Savings vs Compliance Risks
Third-party support can reduce annual support fees by 50% or more, extending the life of existing software investments without forced upgrades. However, enterprises must ensure strict compliance with Oracle's licensing rules when engaging a third party. The court rulings have largely mapped out the dos and don'ts, reducing uncertainty — but diligent CIOs should work closely with legal counsel and their provider to stay within boundaries.
Vendor Relationship Dynamics
Oracle's aggressive pursuit of this case signals that major software vendors will fiercely defend their revenue streams and IP. Customers who opt for third-party support should expect a potentially strained relationship with Oracle. Oracle typically denies access to new software updates, patches, and support once you leave its maintenance programme, and reinstating Oracle support later can require back-payment of lapsed fees. However, the fact that Oracle lost most claims and eventually settled may also moderate its approach.
The resolution of Oracle vs Rimini Street fundamentally changes the negotiation dynamic. Knowing that third-party support is a legally validated alternative gives CIOs real leverage: enterprises can negotiate better terms with Oracle by credibly evaluating a switch. Simply having a third-party option on the table has been shown to yield Oracle concessions on pricing, contract flexibility, and upgrade timelines.
Industry-Wide Implications
Beyond Oracle, this legal saga sends a message across the enterprise software industry. SAP faced a similar case years ago (Oracle vs SAP/TomorrowNow, which resulted in a $356.7 million settlement). The Oracle vs Rimini Street precedent has established that third-party support providers can survive legal scrutiny if they develop rigorous compliance processes — potentially encouraging a more competitive market for support alternatives across all enterprise vendors.
For a detailed comparison of the major providers operating in this space, see our guide to Major Oracle Third-Party Support Providers.
Cost and Support Comparison: Oracle vs Third-Party
One of the primary drivers behind the Oracle vs Rimini Street conflict was the promise of cost savings. Third-party support can provide significant financial relief, but there are trade-offs. The table below compares the key dimensions that CIOs must evaluate.
| Aspect | Oracle Premier Support | Third-Party Support |
|---|---|---|
| Annual Fee | ~22% of licence cost per year (standard) | ~50% lower than Oracle's fee (approximately 11% of licence value) |
| Annual Increases | Regular uplifts of 3–8% per year | Typically flat or tied to minimal inflation; many contracts lock rate |
| Supported Versions | Current and recent versions only; older versions require costly extended support or are unsupported | Supports older versions indefinitely, even after vendor end-of-support, with custom patches for tax, legal, and regulatory updates |
| Scope of Support | Standard software issues; limited or no help with customisations or integrations | Broader scope including bug fixes, performance tuning, and assistance for customisations; no access to Oracle's new patches, but provides workarounds and fixes |
| Upgrades & New Features | Access to new patches, updates, and upgrade rights while on support; Oracle often pushes upgrades to latest versions | No direct access to Oracle's new patches or major upgrades; focus is on maintaining current system; upgrades are optional |
| Service Quality | Tiered ticket system; can be slow for non-critical issues; no support for custom code | Dedicated senior engineers; often faster response times; will troubleshoot custom code and integrations |
| Contract Flexibility | Leaving Oracle support incurs reinstatement penalties (back-support fees); contracts often tied to all Oracle products | Typically more flexible annual contracts; can cover only selected systems; easier to negotiate terms |
| Compliance Risk | None — using vendor's own support channel | Requires compliance diligence; provider must follow licence rules as clarified by the legal case; choose a reputable provider |
📊 Cost Scenario: $5 Million Oracle Support Bill
A Fortune 500 company pays $5 million annually in Oracle support fees, subject to 5% annual uplifts.
5-Year cost with Oracle: $5.0M + $5.25M + $5.51M + $5.79M + $6.08M = $27.63 million
5-Year cost with third-party support (50% savings, flat rate): 5 × $2.5M = $12.5 million
For a detailed provider-by-provider analysis, see our guide to Spinnaker Support and Oracle Third-Party Support, or our broader assessment of Third-Party Support for Oracle Middleware and Apps.
Recommendations (Practical Tips for CIOs)
| # | Recommendation | Why It Matters |
|---|---|---|
| 1 | Thoroughly review licence agreements: Before engaging a third-party provider, have licensing experts review your Oracle OMA and ordering documents. Verify which environments and software copies the provider can use. | Prevents compliance exposure and ensures you and the provider clearly understand contractual boundaries |
| 2 | Vet the provider's compliance practices: Ask how they deliver services — do they avoid sharing Oracle code between clients? Do they follow the injunction guidelines from the Oracle vs Rimini Street case? | A reputable provider will be transparent about its compliance model; this diligence protects your organisation from inherited legal risk |
| 3 | Secure software assets before switching: Download all relevant patches, updates, and documentation while still on Oracle support. You may lose access to Oracle's support portal after termination. | Having a repository of official updates for your current version is valuable and typically permitted for licensees |
| 4 | Consider hybrid approaches: Maintain Oracle support for critical systems and use third-party support for stable, less-critical systems or older modules. This tests quality on a smaller scale first. | Balances risk and reward; allows you to evaluate service quality before committing the full estate |
| 5 | Leverage negotiation power: Use the credible option of third-party support as leverage in Oracle renewal negotiations. Oracle sales teams are often authorised to offer discounts when they know a customer is seriously evaluating alternatives. | Even if you ultimately stay with Oracle, this tactic routinely yields 15–30% concessions on support pricing |
| 6 | Plan for the long term: If you switch, be prepared for Oracle to withhold upgrades. Ensure your business can operate on its current software version for an extended period and have a roadmap for eventual modernisation. | Third-party support buys time and budget — but you need a strategic exit plan, whether that is cloud migration, SaaS adoption, or a return to Oracle support |
| 7 | Stay informed on legal developments: Although this case is settled, the landscape can evolve. Monitor new rulings, Oracle policy changes, or licence term modifications that may affect third-party support. | Oracle may revise contract language in new agreements to discourage third-party support — proactive awareness lets you negotiate protections |
Evaluating Oracle Third-Party Support?
Our independent advisory team helps enterprises assess, negotiate, and transition to third-party support — or use the option as leverage for better Oracle terms. We work exclusively in your interest, never for the vendor.
Checklist: 5 Actions to Take
- 1Assess Your Support Needs: Inventory your Oracle-based systems and identify which are stable and can be maintained without frequent vendor updates. Older ERP modules that do not require new features are the strongest candidates for third-party support.
- 2Crunch the Numbers: Calculate current annual Oracle support costs (including escalating uplifts) and compare against third-party quotes. Factor in hidden costs of Oracle support (forced upgrades, shelfware support) versus third-party (potential one-time transition costs, future reinstatement fees if returning to Oracle).
- 3Review Contracts and Compliance: Have your legal team review Oracle licence agreements — particularly the Oracle Master Agreement (OMA) — to ensure moving to third-party support won't violate clauses or trigger unwanted consequences such as audit escalation or reinstatement penalties. Engage a licensing expert if needed.
- 4Engage Stakeholders: Discuss the plan with application owners, the CFO (for cost approval), and risk/compliance officers. Ensure everyone understands the benefits (cost savings, extended support life) and the responsibilities (maintaining compliance, relying on an alternative support channel).
- 5Select and Pilot a Provider: Choose a third-party support provider with proven Oracle expertise and compliance practices. Consider starting with a pilot on a non-mission-critical system. Monitor service quality and compliance during the pilot before migrating more critical systems.