How the Reinstatement Fee Works
Oracle support reinstatement fees exist to make leaving support expensive to reverse. When support lapses and you want it back, Oracle charges a reinstatement fee of 150% of the net support fee that would have been charged for the lapsed period — plus the current year's full support fee on top. The policy is published in Oracle's Technical Support Policies and applied consistently, which is why dropping support without a plan to return is one of the most expensive reversible decisions in an Oracle estate.
The logic is deliberate. Oracle's annual support runs at roughly 22% of the original net licence fee and is its highest-margin revenue, so the company protects it aggressively. Treat the reinstatement clause as the price of optionality: the moment you stop paying support, you are not just saving the annual fee, you are accepting a 150%-plus surcharge to ever turn it back on. This sits at the centre of the support strategy in our advanced Oracle licensing guide.
How the Cost Compounds
The penalty grows with every year you stay off support, because the 150% applies to the entire lapsed period. The arithmetic is stark on a real-sized line.
| Scenario | Calculation | Reinstatement cost |
|---|---|---|
| $500k support, back after 1 year | (1 × $500k × 150%) + $500k | $1,250,000 |
| $500k support, back after 3 years | (3 × $500k × 150%) + $500k | $2,750,000 |
| $500k support, kept running 3 years | 3 × $500k | $1,500,000 |
On this line, returning after three years costs $2.75m against the $1.5m you would have paid by simply keeping support live — a $1.25m premium for the round trip. That gap is exactly why the reinstatement clause functions as a deterrent rather than a fee, and why any plan to drop support has to assume you will not be coming back through Oracle's front door.
The Matched-Set Repricing Trap
Even partial reductions carry a trap. Oracle's matching service levels policy requires every licence in a licence set to be supported at the same service level — you may not support a subset of licences within a set. If you terminate support on part of a product family, Oracle reserves the right to reprice the remaining licences at current list, stripping the volume discount you originally negotiated.
An enterprise bought 100 Database Enterprise Edition processor licences at a 40% discount, with support of $627,000 a year for all 100. Terminating support on 40 licences repriced the remaining 60 at a reduced discount — support of $501,600 a year. A 40% cut in licences delivered roughly a 20% cut in support. The matched-set rule ate the rest.
This is the same mechanism that makes post-migration support reduction so hazardous if done naively, and it is why stranded licences from a cloud move must be assessed as licence sets, not individual lines. Never terminate part of a set without modelling the repricing on what remains.
Four Ways to Avoid the Penalty
The penalty is avoidable, and the strongest route is to never trigger it. First, move to third-party support rather than going unsupported. Providers such as Rimini Street, Spinnaker Support and Origina typically cost 50–60% less than Oracle and sidestep the reinstatement clause entirely, because you never lapse — you transfer. Second, negotiate the fee directly. Despite the published 150%, Oracle reps have discretion, with approvals, to reduce or even waive the reinstatement portion to win back a strategic account.
Third, use new spend as leverage. Oracle's sales teams are eager to sell cloud and new licences, and will often forgive or discount reinstatement fees when they are bundled into a fresh OCI or licence purchase. Fourth, clean up compliance before you return. Any re-support triggers a compliance review, so identify and resolve unlicensed usage first — the same discipline that governs the audit exposure a return to support inevitably invites.
Making the Support Decision Safely
The support decision and the licence-deployment decision are inseparable. Before terminating anything, confirm whether the licences are needed for future redeployment or BYOL — terminating support forfeits the right to reuse them in the cloud. Model the matched-set repricing on every remaining set. Decide upfront whether third-party support or a negotiated Oracle position is the destination, because the cheapest path is almost never "lapse and return". The same rigour anchors the Oracle vendor intelligence hub and our broader cost-reduction work.
For the full support-optimisation model — the third-party transition checklist, the matched-set calculator and the reinstatement-negotiation script — download the Oracle Negotiation Playbook, or request a confidential briefing before you submit any support cancellation to Oracle.