What does unused Oracle support actually cost?
Unused Oracle support costs roughly 22 percent of the net license fee each year, escalating annually, so every license left under support but no longer in use is a recurring charge that compounds quietly on the renewal. The licenses themselves are usually perpetual, which means the software keeps working whether or not support is paid, but the support stream renews each year regardless of whether anyone calls a support line or downloads a patch. That is the trap of shelfware: the cost is automatic, the value is zero, and nothing forces a review unless someone goes looking.
Because the fee escalates, the cost of inaction grows. A set of unused licenses left untouched costs more this year than last, and more next year again. The recurring nature is exactly why support optimisation is a standing discipline rather than a one off cleanup. This topic links up to the Oracle negotiation guide, and it sits beside shelfware, finding and shedding it.
How do matching service levels constrain termination?
Matching service levels constrain termination because Oracle's policy requires every license within a defined support set to carry the same support status, so you generally cannot drop support on the unused licenses while keeping it on the ones still in production. This is the rule that catches buyers who assume they can simply stop paying for the licenses they no longer run. If the unused licenses share a support set with active ones, terminating support on the unused portion would, under the policy, require terminating it on the whole set, which is rarely what anyone wants.
The policy exists to stop exactly the optimisation buyers most want to make, which is to keep support on what they use and drop it on what they do not. But the constraint is a structuring problem, not a wall. How the licenses are grouped into support sets is often a function of how they were ordered and renewed over time, and sets can sometimes be separated so the unused licenses sit in their own set that can be terminated independently. The detail is contract dependent and turns on the specific ordering documents, which is why the support sets are mapped before any termination is attempted. For the recurring spend picture, read the support mistakes that lock in cost.
| Situation | Effect of the rule | Buyer response |
|---|---|---|
| Unused licenses share a set with active | Cannot drop part of the set | Separate the set if the contract allows |
| Unused licenses in their own set | Set can be terminated cleanly | Terminate and capture the saving |
| Set structure unclear | Contract dependent | Map the ordering documents first |
How do you structure a clean termination?
You structure a clean termination by mapping the support sets to the ordering documents, confirming which licenses are genuinely unused, and separating the unused licenses into a set that can be dropped without affecting the active ones. The first step is evidence: establish, with deployment data, which licenses are actually not in use, because the saving is only real if the licenses are genuinely shelfware and not simply licenses someone forgot were running. Then read the ordering documents to understand how the sets are constituted, since the matching service levels rule operates at the level of those sets.
Where the unused licenses can be separated, the termination is straightforward and the recurring saving is captured. Where they cannot be cleanly separated, the question becomes whether the saving on the unused portion justifies restructuring, or whether another route, such as trading the unused entitlement into a future negotiation, serves better. Termination also has a forward consequence worth weighing: re entering support later carries a penalty, so the decision is made knowing the cost of reversing it. The point throughout is that this is a contract and structuring exercise, resolved on the documents, not a simple instruction to stop paying.
Matching service levels means every license in a support set shares one support status. Terminating support on the unused licenses requires structuring them into a set that can be dropped on its own.
Our support cost reduction guide maps your support sets, confirms genuinely unused licenses, and structures a termination that survives the matching service levels rule. Fixed Fee or Gainshare, with no risk to you.
What is the buyer move on unused licenses?
The buyer move is to map the support sets against the ordering documents, prove which licenses are genuinely unused with deployment data, and structure the termination so the matching service levels rule does not force you to keep paying on the whole set. Establish the unused portion first, because the saving has to be real. Read how the sets are constituted, since the rule operates at that level and the answer is contract dependent. Separate the unused licenses into their own set where the contract allows, and weigh the recurring saving at roughly 22 percent against any future re entry penalty before you act. To do this across your estate, work across to re entering support, the penalty math and up to the Oracle negotiation guide.
FAQ
Can you drop support on some licenses and keep the rest? Only if they can be separated into their own support set, because matching service levels requires every license in a set to share one status.
What does support cost? Roughly 22 percent of the net license fee each year, with annual escalation.
What is the buyer move? Prove the unused portion, map the sets, and structure the termination so the rule does not force you to keep paying on the whole set.