Support fees continue at the ULA level after certification, whatever number you certify. The fee is anchored to the support base carried from the agreement, not to the certified quantity, which is why a higher certified count is free value and why the fear that certifying more raises support is a myth.
Support is the cost that outlives the ULA. The license fee was paid for the term and is gone; the support stream continues for as long as you keep the perpetual licenses certification produced. Because support is where the long run money sits, it shapes two decisions that matter: how much to certify, and what to do with the support contract once the term has ended. Both are governed by a single fact that is widely misunderstood, which is that the support fee after certification is set by the support base you carried from the ULA, not by the quantity you certify. This article explains how support behaves after a certification, why a larger certified count costs nothing more in support, and what actually drives the bill in the years that follow. The exact wording of your support and repricing terms governs the detail, so confirm the points here against your own agreement.
No. Support fees continue at the ULA level after certification regardless of how many licenses you certify. The annual fee was fixed by the support base established when the ULA was signed, and certification converts unlimited deployment into a perpetual quantity without changing that base. Certifying two hundred processors or six hundred carries the same support cost, so every additional license you legitimately certify is permanent entitlement gained at no extra support. The persistent worry that a higher count will trigger a higher bill is a myth, and it is unpicked in detail in the support repricing myth debunked and why support stays flat at certification.
When a ULA is agreed, a support base is established, usually carried forward from the licenses and support that preceded the agreement. That base, plus the contractual annual uplift, is what you pay. Certification does not recalculate it against the new perpetual quantity. This is the mechanical reason that maximizing the certified count is value taken at no marginal support cost.
The fear comes from intuition about ordinary license purchases, where more licenses mean more support. A ULA does not work that way at certification, because the support fee was decoupled from quantity when the agreement was signed. Carrying ordinary purchasing intuition into a certification leads teams to certify conservatively and leave permanent value unclaimed, which is exactly the wrong move against a fixed fee.
After certification the support cost is driven by two things: the support base carried from the ULA, and the annual uplift applied to it under your contract. The certified quantity does not enter the calculation. This is why the practical work on support after a ULA is not about the count at all but about the base and the uplift, and about whether the support you keep paying still matches the licenses you actually use. The detail of how that fixed fee is structured appears in support fees do not rise with the count.
The uplift is a percentage added to the support fee each year, and over a long horizon it compounds into a meaningful sum. Because the fee is fixed against quantity but grows against time, the long run support cost is largely a function of how many years you hold the licenses and what uplift applies. Modeling that horizon is part of any sound exit plan.
A certification can leave you holding perpetual licenses you no longer deploy, and support continues on the full certified set unless you act. Whether and how support can be reduced on genuinely unused licenses is a separate question with real constraints, and it is one place where the support bill can sometimes be addressed. The reallocation of certified licenses across the estate is covered in license reallocation after certification.
An indicative database ULA carries a fixed annual support base set when the agreement was signed. At certification the team first expects to certify 300 processors, then, after cloud, disaster recovery, and non production deployments are counted properly, certifies 540. The support fee is identical in both cases, because it follows the support base, not the certified quantity. The 240 additional perpetual processors are gained at no extra support cost. Over a ten year horizon the only support movement comes from the annual uplift applied to the fixed base, not from the larger count. The figures are indicative; your support base and uplift come from your own agreement.
The two ideas combine into a simple posture. Because the certified count does not move support, certify everything you are genuinely entitled to, since each additional license is free permanent value. Then treat the ongoing support stream as a separate management task, focused on the base, the uplift, and the match between what you pay support on and what you use. Conflating the two, by under certifying out of a fear that does not apply, gives away value on the licensing side without saving anything on the support side.
One contractual rule deserves early attention, because it constrains how support can be restructured after certification. Oracle generally requires that licenses sharing a support agreement keep matching service levels, which limits selective dropping of support on part of a set. The mechanics and the room it leaves are set out in the matching service levels rule, and they should inform any plan to trim the support bill.
Support after a ULA certification is fixed against the certified quantity and driven instead by the support base and the annual uplift, so the right move is to certify fully and then manage the support stream on its own terms. Start with the post certification audit guide for the wider post exit picture, understand the constraint in the matching service levels rule, and explore options in license reallocation after certification. Because your support base, uplift, and repricing terms are specific to your agreement, confirm the cost behaviour here against your own contract before acting.
No. Support fees continue at the ULA level after certification regardless of the certified count. The fee was fixed by the original ULA support base, not by the quantity you certify, so a higher certified number adds perpetual licenses at no extra support cost. The fear that certifying more raises support is a myth.
After certification the support stream is anchored to the support base carried from the ULA, typically uplifted each year by a contractual percentage. It is the original support base and the annual uplift that drive the cost, not the certified quantity, which is why maximizing the count is free value against a fixed fee.
We help you maximize the certified count at no extra support cost, then model the base and the uplift so the support you carry matches the licenses you actually use.