Full narration of the briefing. Click a section heading to jump the player to that moment.
The certification letter arrives, the ULA fee stops, and most organisations treat that as the end of the story. It is not. It is the start of a position you will hold for the next decade, and the decisions available to you on day one are much wider than the ones you had a month earlier. I am Claire, Daniel is with me, and this session is what you now own, what it costs to keep, what the count actually constrains, and the options that certification hands back to you.
Getting this part right is worth as much as the certification itself.
Start with the bill, because it does not stop. You now hold perpetual licences, and perpetual licences carry annual support. Oracle's published rate is twenty two percent of licence value each year, and uplifts of three to four percent a year are common. Compound that.
Ten years of support on a certified position, at twenty two percent rising three percent annually, comes to roughly two and a half times the licence value itself. That is the real cost of the estate you just certified, and it is the number your finance team should be looking at, rather than the ULA fee you have stopped paying.
Now the constraint, and this is where organisations get caught. During the ULA, deployment was unlimited and nobody had to think about a number. From certification day, your certified quantity is a ceiling. Deploy beyond it and you are unlicensed, in exactly the way you were not the week before.
The habits built over three years of genuinely unlimited use do not switch off by themselves, and the teams deploying databases usually have no idea the rules changed. That gap, between a fixed entitlement and an unchanged deployment culture, is the most common source of Oracle exposure we see after a certification.
So governance has to arrive with the certificate, and it is not complicated. Three things. A published entitlement position, so anyone can see what you hold, product by product. A gate in your provisioning process, so a new Oracle instance requires a check against that position rather than just a form.
And a quarterly reconciliation, so drift is found in months rather than at an audit three years later. Any organisation that can do change management can do this. What kills it is nobody owning it, because the person who ran certification usually goes back to their day job the week after.
Now the upside, because certification restores choices that were unavailable while the ULA fee was running. You can consolidate onto fewer processors and reduce your support bill, because you own the licences and can shelve what you do not use. You can consider third party support on the licences you no longer want Oracle to maintain. You can migrate workloads without wondering how it affects an unlimited grant.
And you can shrink deliberately, reducing the supported estate year on year, which a running ULA quietly discourages because everything feels free while the fee is fixed. Each of those is worth modelling in the first year.
Audit risk changes shape too, and it is worth naming. During the term, an audit was largely academic for the covered products, because your deployment was unlimited. After certification, an audit is a comparison between your certified numbers and your current deployment, and any growth since the count is exposure. Expect the interest to increase rather than decrease once a ULA ends.
The defence is the governance we just described, plus the certification evidence file kept intact rather than archived and forgotten. Keep it for the life of the licences, which in practice means indefinitely.
The move from this briefing: within thirty days of certifying, publish your entitlement position, name its owner, and put a provisioning gate in front of new Oracle deployment. Then model your support bill over ten years, because that number will surprise your finance team and it is the one that funds every optimisation project you want to run afterwards. Next session is the last one: the whole series in one place, and how to get help if you want it. See you there.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Oracle negotiator