Exiting Oracle support to Rimini Street is a 50%+ saving — and the most predictable audit trigger Oracle has.

Why the exit math works — and where it breaks

The core economics of exiting Oracle support to Rimini Street are simple. Oracle Premier Support is billed at 22 percent of net licence list per year, uplifted by CPI annually. Rimini Street prices their service at roughly 50 percent of your current Oracle support bill. The arithmetic gets stronger every year because Rimini Street caps inflation in their multi-year agreements, while Oracle Premier Support compounds.

For a customer paying $4M in annual Oracle Premier Support today, the modelled run-rate over five years is roughly:

The math breaks in two scenarios. First, if you plan to be back on Oracle Premier inside three years — for example, because a major upgrade or a cloud migration requires it — Oracle's reinstatement fees will erode most of the saving. Second, if the audit cost of the trigger settlement exceeds the savings, the exit was the wrong call. Both are defendable with the right preparation; both are fatal without it.

What Rimini Street actually delivers

Rimini Street's scope is broader than the "patches and break-fix" framing it sometimes receives. For Oracle Database, E-Business Suite, JD Edwards, PeopleSoft, Siebel, and the Hyperion family, Rimini Street typically provides:

• Tax, legal, and regulatory updates — for E-Business Suite, JD Edwards, and PeopleSoft, this is the largest delivered value. Rimini's local-country tax updates are warranted in their contract.
• Custom security patches — Rimini Street does not deliver Oracle's CPUs, but they deliver their own security analysis and remediation. Their model is configuration-and-control-based rather than universal patch.
• Named senior engineer assignment — a single Primary Support Engineer per customer, generally with 10 to 15+ years' experience on the product line. Different model from MOS ticket routing.
• Interoperability and platform support — they will support your Oracle release on newer OS, virtualisation, and browser versions even after Oracle's compatibility matrix has stopped being updated.
• Performance and customisation support — historically excluded from Premier Support, included by Rimini.

What you do not get from Rimini: Oracle-delivered Critical Patch Updates, Oracle My Oracle Support knowledge base access, Oracle-delivered installation media for releases obtained after the support termination date, and certain certifications that require an active Oracle support contract.

What you lose when you leave Oracle Support

This is the section finance and CIOs usually under-plan. The savings are real, but so are the lost entitlements. Map them before you sign.

• Oracle CPUs and one-off patches — Critical Patch Update access stops at the support termination date. Plan to download every patch you might need before that date, including major-version installers you have a right to under your existing licence.
• My Oracle Support (MOS) — full access ends with the support contract. Some read-only artefacts may remain accessible briefly, but never plan around them.
• Oracle's upgrade entitlements — your perpetual licence remains, but rights to future major versions (e.g. moving from Database 19c to 23ai later) are tied to active support. Lapsing support locks you to the major version you held at the termination date.
• Oracle Engineered Systems firmware and Exadata updates — if you run Exadata, ZDLRA, or other engineered systems, Rimini Street can deliver some platform support but firmware is supplied by Oracle. This is the single biggest "do not exit" reason for many estates.
• Cloud benefit programmes — Support Rewards (the 25 percent OCI consumption credit linked to Premier Support) ends with the support contract. If you have committed OCI consumption, model the loss before you exit.

The audit trigger and how to defend it

An Oracle support termination notice is the most reliable LMS trigger we see — more predictable than a ULA expiry, more predictable than a virtualisation environment change, more predictable even than a Java SE non-renewal. The buyer-side counter is to stage the audit-defence pack and the licence-position evidence before the termination letter goes out — the Oracle Support Termination Pre-Flight Checklist walks through the 90-day pre-flight day-by-day. Three audit-trigger patterns recur:

1. The "courtesy review." Within 30 to 90 days of your non-renewal notice, an LMS engagement letter arrives framed as a routine review. It is not routine. The review's outcome is almost always a back-licence claim covering perceived under-licensing across the entire estate — not just the products you dropped.
2. The audit by another route. If the formal review approach is declined, Oracle may pivot to a Java SE Universal Subscription audit (now possible across the entire employee population) or an OCI consumption review. The exit decision survives — but you have to defend a different battlefield.
3. The "reinstatement squeeze." Two to three years after the exit, Oracle's account team approaches with a "limited-time" reinstatement offer at reduced back-fees. This is almost always a trap to re-anchor the contract before a larger negotiation — most often a Java or OCI deal.

Defence is buyer-side, evidence-based, and starts before the exit notice goes out. The minimum evidence pack: an Effective Licence Position covering every Oracle product family, virtualisation configuration documentation (with hard-partitioning evidence where claimed), Named User Plus counts mapped to identifiable individuals, Java SE deployment inventory, and a written decommission record for any installations that have been removed. With that pack on the desk, settlement outcomes typically land between 15 and 30 percent of Oracle's opening claim. Without it, the average is closer to 60 to 75 percent.

Contract rules: CSI, matching service levels, reinstatement

Three contract mechanisms determine what you can and cannot do.

Customer Support Identifier (CSI). Your Oracle support contracts are grouped under CSIs — each CSI is the smallest unit you can renew or cancel. You can drop one CSI and keep another. You cannot drop part of a CSI. Most enterprises that have grown by acquisition hold multiple CSIs, which gives the most exit flexibility.

Matching Service Levels. Inside a single CSI, all licences of a given product family must carry the same support level. You cannot keep half of your Database EE Processors on Premier and drop the other half. The clean exit at CSI level is: drop everything inside that CSI, or keep everything inside it. Plan the architecture before you negotiate.

Reinstatement. Oracle's standard reinstatement policy charges back-support fees covering the lapsed period (typically at 150 percent of the unpaid support amount) plus a 50 percent reinstatement fee on top. For a $4M annual support spend lapsed for two years, reinstatement can exceed $14M. This is intentional — Oracle wants the exit to be one-way. Plan accordingly.

The contract-driven exit shape that works best for most enterprises: identify the CSIs where Rimini Street can support the workload, drop those CSIs in full at their next renewal date, keep on Premier Support any CSI containing Engineered Systems firmware-dependent product or critical compatibility commitments, and run the two support models in parallel for the remaining contract term.

Patches, CPUs, and the "stay on this version" decision

The most under-discussed aspect of an Oracle support exit is the implicit decision to stay on a specific major version for several years. Rimini Street will support older releases of Oracle Database, EBS, JD Edwards, and PeopleSoft long after Oracle's Extended Support has ended, but you forfeit the right to in-place upgrade to a new Oracle major release while off Premier Support.

For most enterprises, this is a feature, not a bug. The cost and disruption of a Database 19c-to-23ai upgrade, or an EBS 12.2 to Fusion Cloud move, often dwarfs the support saving. Customers who exit Oracle Support typically also commit to a multi-year stability period on the current major release — which is exactly what most operational teams want anyway. For a mid-market worked example pairing stable EBS to third-party support with Java SE migration to Corretto, see the mid-market manufacturer Oracle support reduction case study — a 47% cut locked in over 3 years. For a long-tenured university EBS / PeopleSoft estate that right-sized first, see the higher-education EBS PeopleSoft optimisation case study. For the segmented savings data — by product family, estate size and reinstatement risk — see our Oracle third-party support savings benchmark 2026.

The "patch download" sprint before exit is non-negotiable. Two weeks before the support termination date:

• Download every applicable Critical Patch Update for every product in scope
• Download all installation media for major versions to which you have a perpetual right (including versions you have not yet deployed but may need later)
• Archive all relevant MOS knowledge base articles using documented procedures — this protects operational continuity
• Document the configuration of every Oracle Engineered System, including firmware version and OS version

Rimini Street typically assists with the patch-download sprint as part of onboarding. Build it into the transition statement of work, not as an afterthought.

The 14-step operational exit playbook

This is the sequence we use to defend the savings, defend the audit position, and keep operations running. Skip a step, and you pay for it later — either at audit settlement or at reinstatement.

1. Build the Effective Licence Position covering every Oracle product across every CSI. No exit without ELP.
2. Identify candidate CSIs where the workload is mature, stable, and not dependent on Oracle's roadmap or Engineered Systems firmware updates.
3. Model the run-rate carefully. Include the loss of Support Rewards, Cloud Benefit Programmes, and any Premier Support-dependent contractual benefits.
4. Quantify the audit exposure from current compliance position. The exit makes sense even with audit risk built in — but only if you know what the risk is.
5. Negotiate the Rimini Street SoW before sending notice to Oracle. Lock in the cap, the SLA, the named engineer, and the patch-download sprint.
6. Decide on the Java SE position separately. Java SE Universal Subscription is a different contract and a different audit dynamic.
7. Prepare the audit defence pack. Documented decommission records, NUP mappings, virtualisation configuration, hard-partitioning evidence. File it before the notice goes out.
8. Run the patch download sprint two to four weeks before the support termination date. Verify completeness with Rimini's onboarding team.
9. Send formal non-renewal notice in writing, on the contractually required day (typically 30 to 90 days before renewal anniversary).
10. Cut over to Rimini Street on the support termination date. Onboarding is typically two to four weeks; their team integrates with your operations team.
11. Respond to the LMS engagement letter if and when it arrives. Buyer-side, evidence-based, negotiate from a defended position.
12. Renegotiate database options and adjacent licences at subsequent renewal dates. Many customers find Partitioning, Advanced Compression, or Diagnostics Pack lose their justification once the BI tools, Engineered Systems, or specific applications change scope.
13. Reinvest the savings deliberately. A portion of the saving funds the migration projects that protect the exit — replatforming, modernisation, audit-defence retainer.
14. Review the exit at year 3. Some customers re-enter Premier Support at year 3 to 5 as part of a wider cloud or modernisation move. Plan the re-entry path now so you know the cost if you take it.

When NOT to exit Oracle Support

The exit is not right for every estate. Buyer-side advice means saying no where it would harm the client. Five situations where Oracle Premier Support is the right answer:

1. Engineered Systems firmware dependency. Exadata, ZDLRA, and SuperCluster customers need ongoing Oracle firmware updates. Rimini can support the workload, but the platform updates come from Oracle. Most Engineered Systems customers stay on Premier for the platform CSI.
2. Active major-version upgrade in flight. A live Database 19c to 23ai upgrade, or an EBS 12.2 to Fusion Cloud migration, needs Premier Support access to upgrade media and patches. Complete the upgrade before exiting.
3. Committed OCI consumption with Support Rewards in play. If the Support Rewards programme materially offsets your Premier Support bill, the net saving from a Rimini exit is much smaller than the headline 50 percent.
4. Cloud roadmap inside 24 months. If a documented cloud move will retire the workload inside two years, the exit-then-reinstate cycle rarely pays off.
5. Mid-contract renewal with no triggerable termination date. Some legacy contracts have unusual termination mechanics. Validate the renewal date and CSI structure before assuming the exit is available.

For everyone else — and that is the majority of large Oracle Database, EBS, JD Edwards, PeopleSoft, Siebel, and Hyperion customers — the exit math wins. The question is how, not whether.

FAQ — Exiting Oracle support to Rimini Street

Can we go back to Oracle Premier Support after using Rimini Street?

Yes, but it is expensive. Oracle's standard reinstatement policy charges back-support fees covering the lapsed period (commonly at 150 percent of unpaid support) plus a 50 percent reinstatement fee on top. Plan the exit assuming you will not return — and if you do return, negotiate the reinstatement penalty before agreeing to it.

Will dropping Oracle support trigger an audit?

Frequently, yes. Cancelling Premier Support on any Oracle product line is a well-known LMS trigger. Expect a discovery letter within 30 to 180 days of the non-renewal. Prepare the audit evidence pack before you file the notice — an ELP, install records, virtualisation configuration, NUP counts — so you negotiate from a defended position.

Do we lose access to Oracle patches and CPUs after we leave?

You lose access to Oracle-delivered patches and Critical Patch Updates from the date support ends. Rimini Street delivers their own tax, legal, regulatory updates and security patching, warranted contractually. Download every patch you might need — including major-version installers you have a perpetual right to — before the support termination date.

Can we keep some Oracle support and drop the rest?

Partial drops are restricted by the matching service levels clause. You generally cannot keep half of a CSI on Premier Support and cancel the other half. The clean exit is at CSI level for a defined product family — drop the whole CSI or none of it. Multi-CSI estates can split the decision per CSI, which is the most flexible structure.

What about Java SE — can Rimini Street support that too?

Rimini Street offers Java SE support as a separate service. The decision to exit Oracle Java SE Universal Subscription is independent of the Database or EBS support decision; the audit dynamics are different. Treat it as a parallel project, not a bundled one.

How long does the Rimini Street onboarding take?

For a typical large enterprise: two to four weeks for the operational onboarding (named engineer, ticketing, escalation paths), plus a parallel two to four weeks for the patch-download sprint. The Oracle-side support termination is hard-cutover, so the practical advice is to complete onboarding before the termination date, not after.

Independence statement: Oracle Licensing Experts is an independent buyer-side advisory firm. Not affiliated with Oracle Corporation. We have no commercial relationship with Rimini Street or Spinnaker. All recommendations are evidence-based and protective of the client.

Related guides