Contents
Key takeawaysThe three clausesLicense sets and CSIsReinstatement costPartial drops and repricingSupport versus licensesWhat Oracle will sayWhat we saw, 2024 to 2026Planning timelineWhat to do nextFAQLeaving Oracle support is easy and returning is expensive. Reinstatement costs 150 percent of the last annual fee, prorated across the lapse, so a round trip costs you half as much again as the support you avoided.
- Reinstatement is 150 percent, prorated. Two skipped years on a $2M support line avoid $4M and come back as a $6M fee, plus the new year's support.
- The license set is the unit of decision. It covers a program with its options and packs, and every program sharing source code, whatever CSI it is billed on.
- Most models start on the wrong boundary. In roughly two thirds of our exit reviews, the buyer had scoped the decision around a CSI number.
- Partial drops reprice what you keep. Surviving licenses reprice at list less the standard discount and never fall below their previous fee.
- License terminations are permanent. Support can be bought back at a published price; terminated licenses only at the price on the day.
- Third party support does not stop the clock. Treat a provider as a permanent choice, never a place to wait.
Dropping Oracle support takes nothing more than declining the renewal, and partial reductions add a termination letter. What the drop saves depends on three published clauses. One decides what you can drop, one reprices what you keep, and one sets the price of coming back.
I spent years on the Oracle side of these conversations, and buyers who model all three before the letter do far better than those who find them after it.
Which Oracle support policies decide the cost of dropping support?
Three clauses in Oracle's Software Technical Support Policies decide it: matching service levels, repricing after a reduction, and the reinstatement fee. The policies are published documents, and your ordering documents bring them into the contract by reference, which is why the current version applies at each renewal. The incorporation by reference guide explains how that works.
| Clause | What it says | What it does to the model |
|---|---|---|
| Matching service levels | Support decisions apply to the whole license set: the program plus its options and management packs, or all programs sharing source code | Stops the cherry pick. The unit of decision is the set, and drawing it wrong voids every scenario built on it |
| Repricing after reduction | Surviving licenses on the order reprice at list support less the discount that applies to the smaller volume, with a floor at their prior fee | Stops the partial saving. Dropping half the licenses rarely halves the bill |
| Reinstatement at 150 percent | Return is charged at 150 percent of the last fee, prorated across the lapse, plus the new support period | Adds half the avoided fees to the cost of any round trip, and the clock never pauses |
Why do the three clauses have to be modeled together?
Each clause closes the exit the previous one leaves open. Matching service levels blocks the selective drop. Repricing blocks the partial drop, and reinstatement taxes the temporary drop.
A model that tests one clause at a time always looks better than the contract allows. Run all three against the actual license sets, in the same spreadsheet, before a number goes to your CFO.
What does the repricing cap and floor mean in practice?
The policy sets two limits on the repriced fee. It cannot exceed what you paid before for the whole order, both the licenses you keep and the ones you terminate, plus any country annual adjustment. It also cannot fall below what you already paid for the licenses you keep.
In practice the floor means the licenses you keep never cost less than they did before the cut. The cap is your only protection, and it still allows the fee on the smaller order to rise to the full amount you paid for the whole order, as the worked example below shows.
How to Negotiate Your Oracle SaaS Renewal: The Five Moves at the Table
What is an Oracle license set, and why is the CSI the wrong boundary?
A license set is the unit Oracle applies support decisions to, and it is almost never the same thing as a CSI. The Customer Support Identifier is how Oracle bills you. The license set is how the support policy decides what must stay supported together, and the two are different maps of the same licenses.
Under the policy, a set includes all your licenses of a program with its options, management packs and self service modules, and all licenses of programs that share the same source code. For the database, Oracle names five editions as sharing source code:
- Database Enterprise Edition
- Database Standard Edition
- Database Standard Edition One
- Oracle Database Standard Edition 2
- Personal Edition
So a drop scoped to one CSI can trip matching service levels on licenses three invoices away, as when a Standard Edition 2 server loses support while Enterprise Edition stays supported elsewhere. You may not support part of a set; you reduce it by terminating the unsupported licenses in a termination letter.
How do you check your own license sets?
The work is documentary. Build the entitlement register first, then map it to license sets under the policy definitions, before any scenario is priced. It is the same consolidation the license position guide builds for every other Oracle decision.
- Ordering documents. Every order with its license lines, metrics and quantities. Repricing runs per order, so the order number matters as much as the product.
- My Oracle Support CSI list and renewal quotes. These show which license lines sit on which CSI and what you pay per line today.
- Options and packs in use. DBA_FEATURE_USAGE_STATISTICS shows which database options and packs have been used, and the CONTROL_MANAGEMENT_PACK_ACCESS parameter shows whether Diagnostics and Tuning are switched on. The management packs guide covers how to read both.
- Source code families. Group every database edition you hold, on any order, into one set before you model anything.
The set map also shows where the real savings are: sets that separate cleanly, run fully deployed on stable versions, and have no return scenario worth pricing. The entitlement reconciliation guide walks through matching contracts to deployments.
Oracle Third Party Support Analysis
The clauses, the license set mapping and the reinstatement model in one guide.
Get the white paper →How much does it cost to reinstate Oracle support after a lapse?
Reinstatement costs 150 percent of the last annual support fee you paid, prorated from the date support lapsed to the date you order it back, plus the support fee for the new period.
Take the example from our engagement files. A $2M annual support line, dropped for two years, avoids $4M. Coming back costs $6M in reinstatement plus the new year's support, so the round trip costs $2M more than staying, exactly half of what was avoided.
| Months without Oracle support | Support avoided | Reinstatement fee at 150 percent | Extra cost of the round trip |
|---|---|---|---|
| 6 | $1M | $1.5M | $0.5M |
| 12 | $2M | $3M | $1M |
| 24 | $4M | $6M | $2M |
| 36 | $6M | $9M | $3M |
The ratio never changes with the length of the lapse, and the new period's support comes on top in every row. For any platform that might return, the drop works like a loan of the avoided fees at a fixed 50 percent charge, due in one payment on the day you need support again.
If you never bought support for the licenses, the fee is 150 percent of the net support fee that would have applied, prorated back to the original license order date.
Does third party support pause the reinstatement clock?
No. The clock runs from the day Oracle support ended, whoever supports the systems in between. A buyer who spends two years with a provider and then returns pays the provider for two years and then pays Oracle the full prorated fee.
That makes third party support a destination, and the provider options should be judged on the permanent case. If your roadmap includes an Oracle upgrade within the next few years, price that return now.
Does dropping support on some licenses cut the Oracle bill?
Usually by much less than the share of licenses dropped. When a subset of licenses on one order is terminated, the licenses you keep reprice at Oracle's list price for support minus the applicable standard discount, within the cap and floor described above.
A hypothetical shows the effect. Say one order holds 20 processor licenses of Database Enterprise Edition, bought at 50 percent off the $47,500 list price. Support runs at 22 percent of the net license fee, and you plan to terminate 10 processors you no longer use.
| Step | Calculation | Annual support |
|---|---|---|
| Support before the cut | 20 × $47,500 × 50 percent = $475,000 net license; 22 percent of that | $104,500 |
| Expected by finance | Half the processors, so half the fee | $52,250 |
| Repriced at list, 10 percent standard discount assumed | 10 × $10,450 list support × 90 percent | $94,050 |
| Repriced at list, no standard discount | 10 × $10,450, which equals the $104,500 cap | $104,500 |
In the first repriced case you give up half the licenses to save $10,450 a year, 10 percent of the bill. In the second you save nothing and still lose the licenses. The actual discount Oracle applies depends on the volume left, so ask for the repriced quote in writing before you decide.
Should you terminate Oracle licenses or only the support on them?
In almost every case, stop the support and keep the licenses. Lapsed support can be reinstated at the published price. Terminated licenses are gone, and the only way back is to buy them again at the list price and discount in force on the day, or never.
The confusion arises inside matching service levels. Buyers terminate licenses to shrink the set that must stay supported, then find the licenses they kept repriced and the terminated ones lost for good. No support decision is worth that trade without a model.
Why we disagree with terminating shelfware to cut support
The usual advice is to find unused licenses and terminate them to stop paying support. We disagree, because the repricing clause often hands most of the saving back to Oracle while the termination is permanent.
Get the repriced quote first and check whether those licenses could cover a workload you would otherwise buy for. Terminate only when the written quote shows a saving you accept. The shelfware guide covers redeployment.
Is Sustaining Support a way to save money?
No. Sustaining Support removes rights while the fee continues. You keep the updates, fixes and patches created during Premier and Extended Support, but you get no new updates, no new security patches and no certification with new third party products or versions.
That makes it a rights decision for frozen platforms. The real savings sit a level up, in the support cost analysis and, for buyers inside unlimited agreements, the PULA analysis, where the support stream defines the economics of the whole agreement.
How does the decision change with your situation?
- Frozen platform with a dated decommission. The best candidate, because return is off the table.
- Active platform with upgrades planned. A poor candidate. The upgrade usually forces a return.
- Mixed database editions across several orders. Map the source code family first; one edition can pull the whole group in.
- Permanent move to third party support. Workable when the whole license set goes together and the business accepts no new Oracle versions.
- Inside a PULA or ULA. Model the exit of the agreement before any support change.
What will Oracle's account team say when you plan to drop support?
Expect the conversation to center on risk and on the termination letter. These are the lines we hear most, with the replies that keep the decision on your terms.
- "If you leave, you can never come back." You can, at the published reinstatement fee. Ask for a written reinstatement quote for the exact CSIs and lapse period you are considering.
- "Just drop support on the servers you retired." The policy does not allow part of a license set to go unsupported. Ask Oracle to confirm the license set and send the repricing per order line before any letter.
- "The repricing is automatic; there is nothing to discuss." The formula is policy. The standard discount applied, the order lines affected and the cap calculation are facts you check line by line.
- "Sign the termination letter this quarter so we can close the renewal." Sign once the set map and the repriced quote are agreed. A letter signed first cannot be taken back.
What have we seen in Oracle support exit reviews from 2024 to 2026?
Across the 25 to 35 Oracle support exit and reinstatement reviews I worked between 2024 and 2026, the cash saving was never the hard part. Drawing the boundaries was.
- 2 in 3 started on the wrong boundary. They had drawn the license set around the CSI number and scoped the whole decision on a billing construct.
- Every license termination repriced. Each partial drop that terminated licenses to satisfy matching service levels produced survivor repricing plus a permanent loss.
The successful exits looked alike. They had license sets that separated cleanly, platforms that were truly frozen, return scenarios that were priced and consciously rejected, and savings booked each year as they arrived rather than projected up front.
The failed ones had one thing in common: a letter signed before the set map existed, whose consequences the three clauses then priced exactly as published.
Leaving is a one way decision priced as though it were reversible. The boundary you draw before you drop decides what going back will cost.
When should you start planning before the support renewal date?
Start a year out. The set map and the repriced quotes take longer than the decision itself, and Oracle has no reason to speed them up once the renewal date is close.
| Before renewal | What to do |
|---|---|
| 12 months | Build the entitlement register from ordering documents and map every license to its license set |
| 6 months | Model each scenario against all three clauses and decide which sets have no return case |
| 3 months | Request written repriced quotes and, if relevant, a reinstatement quote; evaluate third party providers on the permanent case |
| 1 month | Check the termination letter line by line against the set map, then sign or renew |
What should you get in writing from Oracle?
- A repriced quote per order. List support, the standard discount applied, and the cap and floor.
- A termination letter limited to exact lines. Order numbers, license lines, quantities and CSIs, nothing broader than your set map.
- Confirmation of the license set. Which licenses Oracle treats as one set for the drop you propose.
- Separate orders on new purchases. Repricing applies per order, so separable workloads on separate orders keep future options open.
The support renewal checklist covers the other clauses worth reviewing at the same renewal.
What to do next
- Map the license sets first. Cover programs, options, packs and shared source code families, from the entitlement register and ordering documents, never from the CSI list.
- Run all three clauses on every scenario. Matching service levels on the set, survivor repricing on the partial drops, reinstatement on any round trip.
- Price the return in full. Use 150 percent prorated, with the clock running through any third party period, and drop only where the answer is never.
- Never terminate licenses to shrink a support set without a written repriced quote. The letter that saves support can destroy perpetual licenses you cannot recover.
- Treat third party support as a destination. Review the legal position and the provider field on the permanent case.
- Get an independent review before you sign. Our Oracle practice can check the set map, the repricing and the letter against the policy text.
Frequently asked questions
What does it cost to reinstate Oracle support after dropping it?
One hundred fifty percent of the last annual support fee you paid, prorated across the entire lapsed period, plus the fee for the new support period. Whatever the length of the lapse, a round trip leaves you paying an extra 50 percent of the fees you avoided.
Can we drop Oracle support on just some licenses?
Only at the license set boundary. Anything smaller means terminating licenses, and the licenses left on that order are repriced at the smaller volume's discount, with a floor at their prior fee. Ask for that repriced quote in writing before deciding.
Does third party support pause the Oracle reinstatement penalty?
No. Every month a provider covered you counts toward the prorated fee. If you expect to return for an upgrade, add the provider fees and the reinstatement fee together and compare the total with staying on Oracle support.
Is Sustaining Support a way to cut Oracle support costs?
No. The invoice stays the same while new patches and certifications stop. It suits a platform frozen for good. Savings come from separating license sets and negotiating the support line itself.
What is the difference between terminating support and terminating licenses?
Ending support leaves you owning the licenses, and a reinstatement fee brings support back. Terminating licenses ends your right to use them, so returning means a new purchase. Every partial drop in our reviews that terminated licenses to shrink a support set paid twice, in survivor repricing and in the lost licenses.
When does dropping Oracle support actually pay?
When there is no realistic return: cleanly separable license sets, systems frozen on stable versions, dated decommission plans, or a permanent move to third party support. Everything else behaves like a loan at 50 percent.
Can we drop support on Standard Edition 2 but keep Enterprise Edition supported?
Not while you keep both. Oracle groups Enterprise Edition, Standard Edition, Standard Edition One, Standard Edition 2 and Personal Edition as programs sharing source code, so they form one license set. Stopping support on the Standard Edition 2 licenses means terminating them.
Do we have to sign anything to reduce Oracle support?
Yes. Oracle requires license terminations to be documented in a termination letter. Check it against your own set map, and make sure it names only the order lines, quantities and CSIs you intend to terminate.