What Oracle ULA certification actually is
For the life of a ULA, you can deploy the covered products as widely as you like, and the upfront licence fee covers all of it. When the term closes, that freedom has to be converted into something countable.
The mechanism is a written declaration: a named officer of your organisation states how many units of each product were deployed on the certification date, and Oracle issues perpetual licences in those quantities. If you are new to the agreement itself, start with what an Oracle ULA is.
For you
The work belongs to you. Oracle does not perform the count, and in most contracts nothing requires you to use Oracle’s measurement scripts to prepare your own statement.
For Oracle
The figure is final in practical terms. It becomes your ceiling for every year after, and the first processor you deploy above it has to be bought at a time when Oracle knows you need it.
The ULA is a buffet with a fixed entry price. Certification is the moment the kitchen weighs your plate, and that weight is all you get to keep eating from afterwards.
Sheshagiri Anegondi
The Best Oracle ULA Is One You Never Renew
A ULA can be certified: you declare what you have deployed and keep those licenses for good, instead of paying more at every renewal.
Short · 0:54Watch on YouTube
Why the certified figure outlasts the agreement
The licence count is only half of what certification fixes. It also decides what your annual support payment is buying. Oracle’s price list sets annual support at 22 percent of the licence price, and on a ULA the support bill carries on after certification.
On a standard ULA, that bill does not move with the number you certify: a higher count simply means each dollar, pound or rupee of support covers more licences.
Important. Annual support is fixed at the beginning of the ULA term. Apart from a possible inflation index, it does not change after certification, and it does not vary with the number of licences deployed and certified.
Reducing that bill later is also harder than most teams expect. Oracle’s technical support policies require every licence in a licence set to sit at the same support level, and if you terminate part of a licence order, support on what remains is repriced at Oracle’s list price for support minus the standard discount.
Because ULA licences are usually deeply discounted, the repriced total can land close to where you started. There is rarely a cheap way to undo a low count or trim an inflated one.
Six clauses decide your ULA certification
Before a single server is scanned, pull these six terms out of your ordering document. Two ULAs that look identical on the cover page can differ on every one of them, so the only reliable source is your own contract text. A recollection from the account team, or a template from another project, does not count.
Clause extraction checklist
| Clause | Question to answer | Why it moves the number |
|---|---|---|
| Window and trigger | How many days, calendar or business, and what event starts the clock? | Sets the hard deadline, and how much time you have to fix errors. |
| Counting test | Must a program be “installed”, or “installed and running”? | Decides whether standby, DR and idle servers count. |
| Entity scope | Which legal entities are covered, and what happens to acquisitions? | Acquired companies count only if the definition reaches them. |
| Cloud treatment | Is authorised cloud included, excluded or averaged? | Determines whether late cloud growth adds anything. |
| Signatory and delivery | Which officer signs, and how must the letter be sent? | A wrong signature or channel can invalidate an otherwise sound letter. |
| Failure consequence | What happens if certification is late or missing? | Reversion to prior licences or, in harsher versions, to zero. |
Where your ULA sits in its wider lifecycle, from entry through renewal or exit, shapes how hard to push on each of these. Perpetual ULAs follow different end-of-term rules and need separate treatment; see ULA or PULA for the difference. If you want the whole exit run for you, see Oracle ULA certification and exit.
What happens if you miss the certification deadline?
In most contracts, a missed window sends you back to whatever perpetual licences you owned before the ULA began. The clause that defines the window usually also defines the trigger, the day-counting convention and the required delivery method, so read it as a single unit.
The cost of reversion grows with every server added during the term. If deployment tripled, you are left with a compliance gap equal to everything above your old entitlement. A harsher variant treats any product you held no licences for before the ULA as zero.
Building a count you can defend
Treat the count as a project with its own owner, budget and calendar, run on tooling you control. Coverage matters more than speed. Oracle requires non-production environments such as development, test and staging to be licensed, so discovery that stops at the production network will understate your entitlement, permanently.
For every server in scope, record three facts. Together they let anyone reconstruct any line of the declaration months or years later, which is exactly what you will need if an audit follows.
Evidence fields per server
| Field | Records | Typical values |
|---|---|---|
| Counting test | Which test the server satisfies on the certification date | Installed and running · Installed only · Excluded |
| Legal entity | Which contracting or affiliated entity owns it | Parent · In-scope subsidiary · Out-of-scope acquisition |
| Location | Where it runs | On premises · Authorised cloud (provider named) |
A twelve-month plan for Oracle ULA certification
Beginning about twelve months before the end date leaves room to find gaps, fix them and still deliver on time. The phases overlap deliberately: reconciliation starts while discovery is still widening.
Phase deliverables
| Phase | Timing | Output |
|---|---|---|
| Contract extraction | M-12 to M-10 | Six-clause summary signed off by legal |
| Full discovery | M-11 to M-5 | Inventory across every subnet and environment |
| Entity and cloud reconciliation | M-7 to M-3 | Scope decisions for acquisitions and cloud estates |
| Evidence pack | M-4 to M-1 | Per-server records with the three evidence fields |
| Letter drafting | M-3 to M0 | Counsel-approved letter, signatory confirmed |
| Delivery and countersignature | M0 to M+1 | Delivered letter and a countersigned schedule |
The cloud trap
Cloud is where contracts diverge most. Many ordering documents written after 2019 either exclude authorised cloud entirely or count it as a trailing average of past usage, and some older ones say nothing at all. Under an averaging clause, capacity spun up in the last few months barely registers, because it is diluted by all the earlier months at a lower level.
The practical lesson: settle what your cloud clause says early, and if it averages, move cloud workloads well ahead of the end date rather than in a final-month push.
Anatomy of the certification letter
A strong letter is short and precise. It goes out on the contracting entity’s letterhead, carries the signature of the officer your clause names, and travels by the delivery method the contract requires. Inside, it needs five elements.
[Contracting entity letterhead]
1Re: Oracle ordering document [number], Unlimited License Agreement term [start] to [end]
2Certification date: [one date, applied to every quantity]
| Program (full Oracle name) | Metric | Quantity |
|---|---|---|
| Oracle Database Enterprise Edition | Processor | [n] |
| [next program] | [metric] | [n] |
4These quantities reflect deployment on the certification date within the licensed entities.
5Please countersign and return the attached quantity schedule.
[Officer named in the clause] · [Title] · [Signature]
- Contract reference. Ordering document number and ULA term dates.
- Certification date. One date, applied to every quantity.
- Product schedule. Full Oracle product names, no internal shorthand, and the metric for each quantity.
- Scope statement. Confirmation that quantities reflect deployment on that date within the licensed entities.
- Countersignature request. An explicit ask that Oracle sign and return the quantity schedule.
How do you certify an Oracle ULA when Java is bundled in?
Start with the ordering document, because the rule for Java is the same as for every other product: you may deploy only what the contract names. If Java SE appears among the ordered programs, count it in the same enterprise-wide discovery as everything else and certify it on the same basis.
If it does not, it sits outside the ULA, and the Java SE Universal Subscription applies instead, priced per employee since January 2023.
The migrate option needs the Java version in front of you. Oracle JDK 25 is free under the Oracle No-Fee Terms and Conditions until September 2028. Oracle JDK 21 from 21.0.13, JDK 17 from 17.0.13, every release of JDK 11 and JDK 8 from 8u211 fall under the Oracle Technology Network licence, which needs a subscription for production use. Our Java license review maps which of those you run.
Handling Oracle’s account team
Expect the conversation to drift towards a smaller figure or a renewal. These are the positions we hear most often, and how to answer them.
Common positions and responses
| You may hear | A measured response |
|---|---|
| “Share the data and we will run our scripts to validate it.” | The contract calls for an officer’s certification. Offer a product-level evidence summary, and direct any formal verification through the audit clause. |
| “Renewing is easier than certifying.” | A renewal still ends the current term. Ask for both options priced side by side and compare them over five years, against an Oracle ULA price benchmark. |
| “Your acquisition is outside the agreement.” | Check the entity definition and the acquisition wording. If it covers the subsidiary, its servers count. If not, seek an amendment before the end date. |
| “We will confirm we received the letter.” | Proof of receipt is not agreement. Ask for the quantity schedule to be countersigned. |
Renew or certify?
| Certify and exit | Renew | |
|---|---|---|
| Current term | Closes with a fixed entitlement | Also closes, replaced by a new term |
| Future growth | Bought separately above the ceiling | Covered for the new term |
| Cost basis | Ongoing support only | New fee plus support, often with uplift |
| Five-year model | Support plus expected purchases above the ceiling | New fee plus support, at quoted (not list) prices |
Terms to win when you sign or renew
If a new or renewed ULA is on the table, spend your negotiating effort on the certification clause. It decides what the entire term was worth.
Weak versus strong certification terms
| Term | Weak version | Ask for |
|---|---|---|
| Window | 30 calendar days, vague trigger | 60 to 90 business days with a defined trigger |
| Counting test | Installed and running | Installed, so standby, DR and idle test servers count |
| Acquisitions | Separate amendment needed | Automatic inclusion above an ownership threshold you set |
| Cloud | Excluded or averaged | Actual size on the certification date |
| Countersignature | Not addressed | Oracle confirms quantities in writing within a stated period |
| Failure consequence | Reversion to zero | Reversion to prior licences, only after a cure notice |
What we see in practice
Across the 30 to 40 ULA certifications I led or reviewed during 2024 and 2025, the letters were rarely the problem. The weaknesses sat in the counting behind them.
Field findings, 2024 to 2025
| Finding | How often | Usual cause |
|---|---|---|
| No countersignature requested | About 4 in 5 declarations | Letter treated as the end of the process |
| Non-production missing from the first draft | More than half of engagements | Discovery limited to production subnets |
| Late cloud capacity barely counted | Wherever a trailing average applied | Cloud growth planned for the final months |
One of them is written up in full: ULA certification at a bank.
Your next six moves
- Extract the six clauses. Window, counting test and failure consequence shape the whole project.
- Discover everything. Every subnet and every environment, including development, test, QA and training.
- Reconcile entities. Test each acquisition against the definition in your contract.
- Settle cloud early. Know whether your clause excludes or averages before planning any migration.
- Draft the letter ahead of time. Confirm signatory, letterhead, date and delivery method with counsel.
- Insist on countersignature. A signed schedule turns your declaration into shared evidence.
Questions about Oracle ULA certification
Does Oracle run the ULA certification count?
No. It is your statement, signed by your officer. Oracle may query it, but the count, the evidence and the timing are yours to determine within the contract.
Can Oracle audit after certification?
Yes. The audit clause in your master agreement survives. From then on, the certified quantities are the baseline Oracle measures against, so keep the countersigned schedule and the evidence pack filed with the contract.
How long is the certification window?
Whatever your ordering document states. Thirty days after the end date is most common, while a sizeable minority allow 60 or 90. Confirm whether the days are calendar or business days, and what starts the clock.
Do non-production servers count?
Yes. Oracle requires licences for development, test and staging environments as well as production, so they belong in the certified figure.
Can cloud deployments be certified?
Only on your contract's terms. Many post-2019 ordering documents exclude authorised cloud or average it, and some older ones are silent. Plan cloud growth well before the end date.
What is a countersigned quantity schedule?
Oracle's signed acknowledgement of the quantities you certified. Without it, a later audit or support dispute starts from a document only you signed.
See more of our analysis in Google: add Rythium as a preferred source
