Support continues at the ULA level after you certify, so a higher certified count never raises it. The work after exit is not stopping the bill from rising but deciding where you can deliberately reduce it, against repricing and matching rules that can quietly undo a saving.
The support bill is the part of an Oracle relationship that outlives everything else. The ULA term ends, the certification letter is signed, and the support line continues, set at the level the ULA fixed and recurring every year. Many ULA holders misunderstand how it behaves, and the misunderstanding costs them twice: once by making them afraid to certify a full count, and again by making them miss the genuine but narrow opportunities to reduce it. This article explains why support stays flat through certification, why that makes a higher count free value, and where you can and cannot reduce the bill afterward. The detail depends on your contract and how your support is structured, so use the framework here and confirm the specifics against your own agreement before you act.
No. Support continues at the ULA level regardless of how many licenses you certify. The fee was fixed by the ULA and is not recalculated against the quantity you declare at exit, so certifying a higher count does not raise it. This is the single most important fact about post exit cost, and it runs against a common instinct. People assume that declaring more licenses must mean paying more support on them, and so they hold their certified number down to keep the bill in check. The opposite is true. The support fee sits where the ULA set it whether you certify a low number or a high one, which means the certified count and the support line are decoupled. Understanding that decoupling is what lets you certify your full defensible entitlement without fear.
Support is fixed by the ULA, not by the count. So the count is free to maximize and the support bill is a separate problem to manage on its own terms.
Because the support fee was fixed by the ULA and is not repriced against the certified quantity. You pay the same support whether you certify a low number or a high one, so every additional defensible license you certify is captured at no extra support cost. This makes the certified count pure value: the licenses are perpetual, they cost nothing more to support, and they raise the entitlement you can deploy against in future. The fear that certifying more raises support is a myth, and it is an expensive one, because it leads organisations to under count their own entitlement and leave perpetual licenses on the table to avoid a cost increase that does not exist. The right posture is to maximize the count for its own sake and treat the support bill as a distinct line to be managed separately.
Sometimes, but carefully, and rarely as simply as it first appears. The obvious lever is to drop support on licenses you no longer use, which on its own would reduce the bill. The complication is that Oracle's repricing rules and its requirement to keep support at a matching service level across related licenses can claw the saving back, repricing the support on the licenses you keep so that the total barely moves. Whether a reduction is real or illusory depends on how your support is grouped, what the contract says about partial termination, and how the remaining estate would be repriced. This is why dropping support is a modeling exercise, not a quick win. Done with the rules understood, a genuine reduction is sometimes available. Done without them, an organisation can terminate support on unused licenses and find its bill unchanged.
| Action | Effect on the bill |
|---|---|
| Certify a higher count | No change, support stays at the ULA level |
| Drop support on unused licenses | Possible saving, subject to repricing and matching rules |
| Keep the full estate on support | The ULA level continues, predictable but flat |
| Reduce without modeling the rules | Risk of a clawed back saving and no real reduction |
Consider an anonymized insurer that certified a large database position and assumed it could trim its support bill by dropping the licenses a retired application no longer needed. On paper the unused licenses represented a clear saving. Once the matching service level rule was applied, the support on the retained estate would have been repriced upward, leaving the total close to where it started. The insurer modeled the rule first, identified the narrower set of licenses where a reduction would actually hold, and acted only on those. The figures are indicative and the outcome depended on the contract, but the sequence is the point: model the repricing before terminating anything.
Managing support is part of the wider cost picture after certification. Read terminating support on unused licenses for the mechanics of a reduction and third party support after a ULA exit for an alternative route to consider. For how support fits the full post exit cost model, see the post certification audit defense pillar.
No. Support continues at the ULA level regardless of how many licenses you certify, so certifying a higher count does not raise your support fee. That is why a higher certified number is free value. The support line stays where the ULA set it, and the question after exit is not how to stop it rising but where you can deliberately reduce it.
Sometimes, but carefully. Dropping support on licenses you no longer use can reduce the bill, but Oracle's repricing and matching service level rules can claw back the saving across the remaining estate. The decision depends on your contract and how the support is structured, so any reduction needs modeling against those rules before you act.
Because the support fee was fixed by the ULA and is not recalculated against the certified quantity. You pay the same support whether you certify a low number or a high one, which means every additional defensible license you certify is captured at no extra support cost. The fear that certifying more raises support is a myth, and it leads organisations to under count their own entitlement.
Book a confidential assessment and we will show you why a full count is free, model where your support bill can genuinely reduce, and flag the repricing rules first.