Certification converts your deployed quantity into a fixed perpetual count and ends the unlimited right. The day after, you hold permanent licenses, flat support, and the evidence file behind the number. Knowing exactly what you own is the first step to protecting it.
The day after you certify, three things are true. You own a fixed perpetual license count for each named product, equal to the quantity you declared. The unlimited right has ended, so growth beyond that count now costs money. And support continues at the ULA level, unchanged by how high your number landed. What you do next decides whether that hard won position stays intact.
You own a perpetual entitlement equal to your certified count, product by product. For an Oracle Database ULA that usually means a fixed number of Processor licenses, and Named User Plus licenses where that metric applied. These are yours to keep, with no expiry, as long as you maintain support. The certification letter and the evidence file are the proof of what you hold, and they are now the most important licensing documents your organisation owns for these products. Store them where they can be found in two years, because that is when you are most likely to need them.
Certification fixes your number permanently and ends the unlimited right at the same moment. From the day after, every deployment beyond the certified count is a purchase, and every deployment within it is fully licensed and defensible.
The unlimited right is gone. During the term you could deploy the named products freely, but that freedom ended with the term. From now on the discipline is the same as standard Oracle licensing: stay inside your count or buy more. Teams that keep deploying as if the ULA were still live drift quietly into unlicensed use, and that gap becomes audit exposure. The shift in mindset, from unlimited deployment to a fixed entitlement, has to reach the people who actually provision infrastructure, not just the licensing desk.
You can deploy up to your certified count without any further cost. Beyond it, you are using unlicensed product and need to acquire more licenses, because the unlimited right ended at certification. The right way to handle growth is to track usage against the certified count and buy deliberately when you approach it, with the purchase planned and negotiated rather than forced. Panicking back into another ULA simply to cover overflow is rarely the best answer and deserves a proper analysis against the cost of buying the licenses you actually need.
Audit risk rises in the first two years after certification. Oracle knows the certified number, and it has an interest in checking whether actual deployment has stayed within it and whether the certified count itself was sound. The evidence file you built at certification is the defense in both cases. It shows that the number was defensible when declared, and it gives you a baseline to demonstrate that current deployment remains inside the entitlement. An organisation that lets the evidence go stale, or never built it properly, walks into that window without its strongest protection.
The table sets out what to hold and what to do once the count is fixed. Treat it as the handover from the certification project to ongoing license management.
| What you own | What to do with it |
|---|---|
| Perpetual count per product | Record it as your entitlement baseline |
| Certification letter | Store with the contract, accessible for two years plus |
| Evidence file | Keep current as your audit defense |
| Flat support position | Review the ongoing cost separately |
| No unlimited right | Track deployment against the count, buy growth deliberately |
Protecting the position is a discipline, not a one off. Read the ULA certification process step by step to see how the evidence file you now rely on was built, and when Oracle pushes back on a certification for how that same file defends the count. For the full picture, the Oracle ULA certification guide covers the exit and what follows it.
You own a fixed perpetual license count for each named product, equal to the quantity you certified. The unlimited right ends. Support continues at the ULA level. You also hold the evidence file behind the count, which is the document that defends the position if Oracle examines it later.
You can deploy up to your certified perpetual count. Beyond that you are using unlicensed product and need to buy more, because the unlimited right ended at certification. Growth past the certified number should be planned and licensed deliberately, not handled by panicking back into another ULA.
Support continues at the ULA level regardless of the certified count, so a higher number does not raise the bill. The support relationship continues, and managing that ongoing cost is a separate exercise from the certification itself, worth reviewing once the perpetual position is fixed.
Book a confidential assessment and we will document your certified position, keep the evidence file current, and watch for the audit risk that follows a ULA exit.