Certifying a higher count does not raise your Oracle support fees. Support continues at the ULA level regardless of the certified number, so a bigger count is free value. The fear that it costs more is the single most expensive misconception in the certification window.
No. Support fees continue at the ULA level after certification regardless of how many licenses you certify. There is no fee for certification itself, and the support stream is set by the original ULA, not by the count you declare in the certification letter. That means a higher certified number is free value: you convert more unlimited deployment into permanent entitlement without any increase in the annual support you already pay. The widespread belief that certifying more will raise your support bill is simply wrong, and acting on it gives away licenses for no saving at all.
Certify everything you can defend. The support you pay is fixed by the ULA, so every defensible license you leave uncounted is value surrendered with nothing gained in return.
The instinct is understandable. For ordinary perpetual licenses, support is a percentage of the license fee, so more licenses mean more support. Teams carry that mental model into the ULA and assume the certified count works the same way, so they hold the number down to protect the support line. But a ULA is structured differently. You paid a fixed fee for unlimited deployment over the term, and your support is calculated against that arrangement, not against the quantity you ultimately certify. Converting unlimited deployment into a perpetual count is the whole point of certification, and the support stream does not move when you do it. The model that is correct for a normal purchase is exactly backwards here.
Because it causes deliberate under certification. A team convinced that a bigger number means a bigger bill will count conservatively, skip environments they could legitimately include, and leave entitlement uncaptured to keep the support figure down. Since the support figure never moves, the only result is permanent loss. The licenses you do not certify do not come back. The unlimited right ends at certification, so anything you could have counted and did not is gone, and if you later need that capacity you have to buy it new at list price. The myth turns a free maximization opportunity into a self inflicted shortfall.
A logistics company approached its database ULA certification intending to count only its core production estate, worried that certifying its full deployment would lift annual support. Once it understood that support stays flat at the ULA level, it counted production, disaster recovery, test, and legitimately included virtual environments. The defensible certified count landed materially higher, with no change to the support fee at all. The additional perpetual entitlement was captured at zero incremental cost. Figures are indicative and the support treatment depends on the specific contract.
Support is governed by your support contract and its renewal terms, not by the certified count, so it is worth being precise about the cases where it genuinely moves. It can rise at the normal annual support renewal under the standard uplift. It changes if you renew the ULA rather than certify, because you are entering a new agreement. And it grows if, after certification, you buy additional licenses beyond your certified entitlement, because those new licenses carry their own support. None of these is triggered by certifying your existing deployment. Counting what you have already deployed and converting it to perpetual licenses leaves the support line where it was. The exact mechanics depend on your specific support and ULA agreements, which is the one thing always worth confirming before you act.
Knowing the myth is a myth removes the only reason to certify conservatively. The right strategy is to maximize the defensible count, capturing every environment you are entitled to include with the evidence to support it, because each one is permanent value gained at no support cost. That is the opposite of the cautious approach the myth encourages, and it is the approach that converts a ULA into the most entitlement it can legitimately produce.
Before your certification window, confirm how your support is calculated and separate it cleanly from the certified count, so the decision is made on facts rather than fear. Start with the post certification audit pillar guide, then read third party support after a ULA exit and optimizing the estate you certified.
No. Support fees continue at the ULA level after certification regardless of how many licenses you certify. There is no fee for certification itself, and the support stream is set by the ULA, not by the certified count. A higher certified number is free value, because you gain perpetual entitlement without any increase in the annual support you already pay. The fear that certifying more raises support is a myth.
Many teams assume Oracle support scales with license quantity, as it does for ordinary perpetual purchases, so they hold the certified count down to avoid a higher support bill. Because support stays flat at the ULA level, that instinct gives away entitlement for no saving. Every defensible license left uncertified is value forfeited at no benefit, which is why the myth is worth debunking before the certification window.
Support is set by your support contract and its renewal terms, not by the certified count. It can change at renewal under the usual support uplift, or if you renew the ULA, or if you later buy additional licenses beyond the certified entitlement, which carry their own support. Certification of your existing deployment is not the trigger. The exact treatment depends on your specific support and ULA agreements.
Book a confidential assessment and we will show you how much defensible entitlement the myth is costing you, and how to certify it all without moving your support line.