An Oracle Unlimited Licence Agreement is only unlimited within its clauses. What certification actually asks of you, where toxic consumption creeps in, and why the measurement work has to start at the beginning of the term rather than the last six months.
An Oracle ULA — Unlimited Licence Agreement — is a time-based contract granting unlimited use of an agreed subset of Oracle products. In practice this “all you can eat” arrangement often ends with organisations paying considerably more for Oracle than they expected, which makes for an uncomfortable conversation with finance.
ULAs typically run for three years. At the start you convert any existing perpetual licensing you hold, and then pay a total support stream fee for each year the agreement is in force. That fee may rise annually by a percentage, and the mechanism should be defined in your contract.
Because of how the agreement is framed, organisations often assume they are free to consume as much of the covered software as they like. If the licences are unlimited and the bill is paid, what is there to worry about?
Quite a lot, as it turns out. Many organisations find themselves locked into a high support stream that is poor value against the products they actually use.
A ULA’s limits are set by its clauses. Some are product and usage related; others concern your organisation, its structure or the term itself. When the term ends you have two options.
Certify. You declare your usage of the covered Oracle products, subject to the certification clause in your agreement. Oracle uses that declaration to determine the number of licences it grants you going forward.
Extend. Extension usually happens when a business realises its Oracle deployment is too complicated to declare with confidence, and buying another three years is easier than facing the measurement problem. At the end of the extension you face the same two choices — on a larger base, with more drift behind you.
The dangers largely come from two failures: not controlling what you deploy, and not establishing the value of the agreement before signing it.
Failing to establish the value of the ULA
The goal is to be confident the fee is good value against what you use. If your Oracle consumption grows during the term — within the agreement’s parameters — a ULA can be far cheaper than buying licences individually. If consumption falls, you will almost certainly overpay. You need a defensible view of current usage and a credible forecast before you can judge the trade.
Toxic consumption outside the ULA
“All you can eat” is a description of the menu, not the restaurant. A ULA does not cover every product, every deployment topology or every affiliate, and the framing lulls people into deploying Oracle software in ways the agreement does not cover. The result is an unexpected bill at the end of the term or, worse, a breach of deployment terms that forces you to certify earlier than planned. The only real mitigation is controlling deployment as it happens.
Failing to control what you have deployed
Leave your Oracle footprint unmanaged and you will struggle to declare usage accurately at the end of the term. That is how organisations end up extending for another three years even when cheaper alternatives exist — not because extension is better, but because they cannot tell Oracle what they used.
Keep failing to declare and you can end up in a cycle of perpetual ULAs. Oracle may eventually demand a declaration regardless, and failing to produce one carries its own financial and legal consequences.
If you do not have a ULA but are considering one, commission an Oracle Effective Licence Position first. An accurate benchmark of current consumption and liability is the only basis on which the offer can be judged, and building it starts the governance discipline you will need for the whole term.
If you already have a ULA but lack full visibility, get the tools and the skills to establish it now. That tells you whether staying in the agreement delivers an acceptable return, and lets you approach the end-of-term declaration knowing what the answer will be rather than discovering it. It also gives you the evidence to push back in an audit.
Visibility is also how you find toxic consumption of products outside the scope of the agreement, while there is still time to reduce or eliminate it before the term ends.
For many organisations, actively managing the ULA is an afterthought — looked at in the final months of the contract, often as a reaction to a cost that has already become unavoidable.
The problem is that by month thirty you have no reliable record of where the software was deployed over the preceding three years. You cannot declare accurately, and you cannot unwind consumption that falls outside the agreement. Both push the number up.
A ULA is not a reason to stop managing Oracle. It is a reason to manage it more closely, because the consequences all land at once, at a date fixed in the contract. If you want the administrative and cost benefits of a ULA, budget for the programme that protects them — whether you run it in-house on your own tools, or contract it out.
Do not assume Oracle’s own scripts will do the job for you. They produce measurement data for Oracle’s purposes, not a management position for yours.
What a tool has to handle before it is useful in a ULA is fairly specific, and it is worth testing candidates against it. CerteroX SAM’s Oracle engine covers options and packs with supporting evidence and the ability to override a detection, processor types and core factors, licence pools with hosting rights and geographic rules, cover-down logic for Enterprise Edition, E-Business Suite responsibilities, and uncapped quantity handling for unlimited agreements — which is the part that lets a ULA be modelled as what it is, rather than as an enormous number typed into a licence record.
Certero is also a verified third-party tool vendor with Oracle License Management Services. In Certero’s own published wording: being a verified third-party toolset means that Oracle’s audit team can accept data from Certero during an official audit, as an alternative to installing Oracle License Management measurement tools. That is a conditional, not a guarantee — but it is a materially different starting position from arriving at a declaration with spreadsheets.
The objective either way is the same: discover and inventory every Oracle deployment, then keep that position current. CerteroX SAM computes a continuous compliance position rather than a point-in-time reconciliation, so the declaration you would make today is always available, not assembled in a panic at the end of the term.
If you do not have Oracle licensing specialists in-house, that expertise can be contracted rather than hired. Certero offers a SAM managed service, and NHS South West London ICB’s ITAM Asset/PSL Manager, Reece Emson, describes what that compresses: “Certero’s SAM managed service allowed us to significantly mature our license posture at a fast pace, something that would have taken 3-4 years without their involvement.”
Whichever route you take, the decision at the end of a ULA — certify or extend — should be a calculation, not a guess.
Other posts covering the same ground.
Microsoft's August 2025 Product Terms changes: Extended Term standardised across programmes, Exchange and Skype for Business Server Subscription Editions, the Exchange and Windows 10 ESU programmes, and the Dynamics 365 F&O enforcement dates.
Renew, rescope or exit — an Oracle ULA gives you three routes and a narrow window to choose between them. The questions to settle first, and a six-point health check to see how ready you actually are.
Java 17 was free under the No-Fee Terms and Conditions only up to Update 12. From 17.0.13 it moved to the Oracle Technology Network licence — and any production use pulls you into a subscription priced on your whole workforce.
Everything argued above is checkable. Name the publisher, the billing account or the platform you would argue with, and the session is built around it — the reasoning attached, not a summary slide.
No gated download at the end of it.