Oracle Third-Party Maintenance: Is Rimini Street Worth the Risk?

Oracle's 22% annual maintenance is one of the most profitable revenue streams in enterprise software. Oracle support revenue accounts for approximately 54% of total Oracle revenue — and it grows automatically, because the maintenance fee is calculated as a percentage of your cumulative licence investment, which only ever goes up.

The dirty secret: most enterprises use Oracle support for almost nothing. Oracle's error correction and patch delivery is available through its support portal. Customers who need custom fixes, deep architectural guidance, or complex problem resolution typically go to third-party implementation partners anyway. Oracle support's primary value — for many customers — is the right to receive security patches.

Third-party maintenance (TPM) providers like Rimini Street argue that they can provide equivalent or superior support at 50-90% less cost. They've signed up thousands of enterprises globally. Oracle has fought back with litigation, access restrictions, and enhanced audit activity against former support customers. The question isn't whether TPM saves money — it clearly does. The question is what it costs you in ways that don't appear on the invoice.

Third-party maintenance providers do not have access to Oracle's source code, support portal, or patch infrastructure. What they offer instead is:

• Custom-engineered fixes: When a bug affects your environment, Rimini Street's engineers create a workaround or custom fix specific to your deployment — they cannot distribute Oracle's official patches
• 24/7 support with named engineers: Unlike Oracle support's ticketing system, TPM providers typically assign named senior engineers to enterprise accounts
• Interoperability support: Help ensuring Oracle software works with newer versions of operating systems, browsers, and third-party software — support that Oracle frequently charges extra for
• Regulatory and tax updates: For business applications like E-Business Suite, TPM providers deliver localised tax and regulatory updates — one of the most cited reasons enterprises stay on Oracle support
• Security vulnerability advisories: TPM providers issue advisories for Oracle's quarterly Critical Patch Updates (CPUs) and help assess whether vulnerabilities affect your specific deployment

What TPM providers cannot provide: Oracle's official patches, access to My Oracle Support (MOS), new feature releases, or the right to upgrade to new Oracle versions. If you intend to upgrade your Oracle database or applications in the near future, TPM may not be appropriate.

The advertised savings range of 50-90% is accurate for most Oracle environments. Rimini Street's standard pricing is typically 50% of your current Oracle support cost in year one. Some enterprises negotiate further reductions, particularly for multi-year commitments or large estates.

These savings compound. Oracle's maintenance fee increases at roughly 3-8% annually (Oracle reserves the right to increase fees with notice). TPM providers typically lock in pricing for multi-year contracts. Over a 5-year period, the total cost difference can be 60-70% even if you eventually return to Oracle support.

Oracle does not make it easy to switch to third-party maintenance. The company has consistently pursued legal action against TPM providers and implemented technical and contractual mechanisms to make switching more difficult. Understanding Oracle's playbook is essential before making your decision.

The Rimini Street Litigation

Oracle has pursued extended litigation against Rimini Street since 2010. The litigation has resulted in multiple judgements against Rimini Street, primarily around how Rimini engineers accessed Oracle's support portal to retrieve materials needed to support customer environments. Rimini Street has substantially modified its processes and continues to operate, but the legal history is a legitimate risk factor enterprises should understand.

Access to My Oracle Support

When you stop paying Oracle support, you lose access to My Oracle Support (MOS) — Oracle's support portal containing patches, bug reports, and technical documentation. This access includes the ability to download patches for your licensed software. Oracle has previously revoked MOS access for customers who switched to TPM, even for software those customers continued to own licences for.

Audit Activity

Multiple enterprises report elevated audit activity from Oracle following their switch to TPM. Oracle's LMS team has a documented pattern of initiating reviews shortly after an enterprise announces intention to leave or actually leaves Oracle support. Our Software Audit Defence team has seen this pattern repeatedly. Oracle's message is consistent: the cost of an unexpected audit compliance gap can quickly exceed the savings from TPM.

Oracle's Contractual Restrictions

Oracle licences typically prohibit third parties from accessing your Oracle environment to provide support. Allowing a TPM provider to do so may technically violate your licence agreement — a risk Oracle has used in litigation. TPM providers have developed work-around methodologies, but the risk is not zero.

The case for TPM is financially compelling, but the risks are real and need honest assessment. The enterprises that have the most negative TPM experiences are those that underestimated specific categories of risk:

Security Patch Risk

Oracle's quarterly CPU (Critical Patch Update) process patches known security vulnerabilities across its product stack. When you're on TPM, you don't receive these patches. Your TPM provider will issue an advisory for each CPU assessing whether the vulnerabilities affect your specific deployment — but their ability to remediate depends on whether a configuration-level workaround exists.

For environments with strict security compliance requirements — financial services, healthcare, government — the inability to apply official Oracle security patches is a genuine compliance risk. Your internal security team and external auditors need to explicitly accept this risk before you switch.

Upgrade Path Risk

If you leave Oracle support and later decide to upgrade your Oracle Database or EBS version, you will need to re-engage Oracle support to access the new version. Oracle may price your return to support on the current maintenance fee schedule — potentially higher than what you were paying before. Some enterprises that left Oracle support have found returning more expensive than expected.

Cloud Migration Complication

If your roadmap includes migrating Oracle workloads to OCI (Oracle Cloud Infrastructure) using BYOL, Oracle support status may affect your cloud pricing. Oracle's cloud discount programmes for BYOL customers typically require active support status. TPM customers may not qualify for certain OCI pricing tiers.

TPM is not right for every Oracle deployment. The decision depends heavily on your technology roadmap, security requirements, and how you actually use Oracle support today.

If you decide TPM is appropriate, you have three broad options: established TPM providers, boutique specialists, or bringing support in-house.

Rimini Street

The largest and most well-known Oracle TPM provider. Serves thousands of clients globally, with specific coverage for Oracle Database, E-Business Suite, JD Edwards, Siebel, PeopleSoft, and other Oracle products. Rimini Street's scale means extensive knowledge base, but the litigation history is a real consideration. Their standard pricing is typically 50% of your current Oracle support fees.

Spinnaker Support

A smaller TPM provider with a strong reputation for account service quality. Tends to attract clients who want more personalised support than Rimini Street offers. Pricing is comparable to Rimini Street. Spinnaker has avoided significant legal conflict with Oracle by being more conservative about what materials their engineers access.

Self-Support

Large enterprises with substantial in-house Oracle DBA capability sometimes opt to exit Oracle support entirely and manage patches and fixes internally. This is the most aggressive approach — and the most demanding. It requires deep internal expertise and a clear security risk acceptance framework. It is most viable for very large organisations with mature internal IT capabilities and Oracle estates that are genuinely stable.

Even if you have no intention of switching to TPM, the credible threat of doing so is one of the most powerful tools in Oracle contract negotiations. Oracle's support revenue is extremely profitable — losing a customer to Rimini Street hurts both in direct revenue and in Oracle's relationship with that account.

The negotiation approach: engage a TPM provider for a formal assessment and proposal. Get a written quote. Bring it to Oracle's renewal conversation with your account team as a documented alternative. Oracle's response to a concrete TPM proposal is almost always to engage on support cost reduction — something they rarely volunteer otherwise.

We've seen Oracle reduce annual support fees by 15-30% for customers who credibly present the TPM alternative. Over a 3-year period, a 20% support reduction on a $1.5M annual bill is $900,000 in savings — with none of the operational risk of actually switching providers. This is the strategy we most frequently recommend in our Oracle negotiation engagements.

The key is credibility. Oracle's account team will probe whether your TPM interest is genuine. It needs to be. Read our guide on Oracle support cost reduction strategies for the complete negotiation framework.

The TPM decision comes down to four factors: your technology roadmap, your security compliance posture, your internal capability, and your Oracle relationship complexity.

Before deciding, answer these questions honestly:

1. Will you upgrade your Oracle software versions in the next 3 years? If yes, TPM complicates your return path.
2. Do you have regulatory obligations that require applying official vendor security patches within a defined timeframe? If yes, TPM may create compliance gaps.
3. Do you have an active or anticipated Oracle audit situation? If yes, resolve it first.
4. Do you have internal Oracle DBA capability to work with a TPM provider effectively? If no, TPM is higher-risk.
5. Have you used TPM as a negotiation lever with Oracle directly? If not, try that approach first — it may deliver the savings without the risks.

If you're uncertain, the most cost-effective path is typically to use the TPM option as negotiation leverage first, and evaluate actually switching only if Oracle refuses to engage substantively on support cost reduction.

Read our full Oracle EA Negotiation Playbook for the complete Oracle contract strategy, or review our Oracle licensing guide for 2026 to understand the current Oracle landscape. For multi-vendor context, see our guide on coordinating Oracle, Microsoft, and SAP negotiations.