Contents
Key takeawaysWhat certification isThe six clause elementsWhat an undercount costsBuilding the countThe certification letterOracle's lines and repliesTerms to negotiateWhat we have seenWhat to do nextFAQOracle ULA certification is a declaration you sign rather than an audit Oracle runs. An officer states how much of each ULA product was installed and running on the certification date, and that quantity becomes your permanent license entitlement.
- You produce the number. Oracle does not count your servers; an authorized officer signs the quantities, and Oracle converts them into perpetual licenses.
- The ceiling is permanent. Every processor deployed during the term is covered, and the first one above the certified quantity is a new purchase at full price.
- Read six clause elements first. The window, counting test, entity definition, cloud treatment, signatory and failure consequence decide the count before discovery starts.
- Non production counts. Development, test, QA and training servers are licensed on the same basis as production and belong in the declaration.
- Missing the window is expensive. The common result is reversion to the licenses you held before the ULA, and some contracts deem zero for products you never owned.
- Ask Oracle to countersign. Roughly four in five declarations we saw went out without that request, leaving the buyer's own letter as the only proof of entitlement.
What is Oracle ULA certification?
Oracle ULA certification is a declaration you sign at the end of an Unlimited License Agreement. An authorized officer states how much of each ULA product was installed and running on the certification date, and Oracle converts those quantities into perpetual licenses. Oracle does not count anything for you.
During the term, every processor you deploy of a ULA product is covered by the fee you already paid. After it, the certified quantity is your ceiling for as long as you hold the licenses, and the first processor above it is a new purchase at full price, made when you have the least room to negotiate.
What does the certified number fix besides the license count?
It fixes what your support payment buys. Support runs at roughly 22 percent of the net license fee a year and continues after certification. On a standard ULA it does not rise with a bigger count, so a full count spreads the same bill over more licenses.
Oracle's support policies also make the bill hard to shrink later. All licenses in a license set must sit at the same support level. Terminating some of them reprices the rest at list support less the standard discount, which on deeply discounted ULA licenses can leave the total close to where it was.
Where does certification sit in the ULA term?
It closes the unlimited term and fixes what you own for the years after. The wider agreement, from entry through exit, is covered in our Oracle ULA guide. The perpetual variant works differently at the end of its term, and our PULA analysis explains how.
The Certification Window
Which ULA clauses decide the number you certify?
Six elements in your ordering document decide the certified number, and you should extract all six before any discovery starts. Two contracts that look alike can differ on every line of this table, so work from your own text. A summary from the account team or a previous project is no substitute.
| Clause element | What to look for | Why it changes the number |
|---|---|---|
| The window | 30, 60 or 90 days; calendar or business days | Sets the last date a reconciliation error can still be fixed |
| The counting test | Installed, installed and running, or in use | Decides whether idle and standby servers count |
| The entity definition | Named entities, ownership thresholds, acquisition language | Acquired companies count only if the definition reaches them |
| The cloud treatment | Silence, exclusion, or a trailing average cap | Can be worth thousands of processors either way |
| The signatory | The officer title and the contracting entity | A letter signed by the wrong person can be challenged |
| The failure consequence | Reversion to prior entitlement, or deemed zero | Sets the true cost of missing the date |
How do "installed", "installed and running" and "in use" differ?
They are three different tests, and each produces a different count from the same servers. Apply the wording in your clause, whatever the last count used.
- Installed. The broadest test. Software present on a host counts whether or not an instance is up, so cold standby servers, idle test machines and dormant Oracle homes are all in.
- Installed and running. An instance must be up on the certification date. A standby server that is installed but shut down drops out.
- In use. The narrowest reading. Expect Oracle to ask for evidence of real workload, and expect idle databases to be questioned.
What happens if you miss the certification window?
You usually revert to the perpetual licenses you held before the ULA started. The same clause that sets the window also sets the trigger, whether days are calendar or business days, and the delivery method.
If your deployment tripled during the term, reversion leaves you with a compliance gap to close. The harsher variant deems zero for products you held no licenses for before.
A renewal still closes the expiring term. It needs either a certification or a roll forward of the old quantities into the new agreement, on terms worth reading before renewal talks start.
How do post 2019 ULAs treat cloud deployments?
Ordering documents written after 2019 commonly exclude authorized cloud environments from the certification, or cap them at a trailing average of usage. Older documents are often silent, so only your own clause gives the answer. The vCPU counting rules for AWS and Azure are in our note on the Authorized Cloud Environment policy.
Oracle ULA Decision Guide
Entry, deployment, certification and the renew or exit decision, set out step by step.
Get the white paper →What does an undercounted certification cost?
An undercount costs the list price of every processor you left out, plus support on each of them every year after. The example below is hypothetical, priced at Oracle's published list price for Database Enterprise Edition: $47,500 per processor, with $10,450 a year for Software Update License and Support.
Say your ULA covers Database Enterprise Edition and you held 40 processor licenses before it started. On the end date, discovery finds 70 processors in production, 50 in development, test, QA and training, and 10 in a subsidiary bought during the term that the entity definition reaches. The full count is 130.
| Outcome | Certified | Uncovered processors | List license cost to close the gap | Support on the gap, per year |
|---|---|---|---|---|
| Full count certified | 130 | 0 | $0 | $0 |
| First draft missed non production | 80 | 50 | $2,375,000 | $522,500 |
| Window missed, reversion to prior licenses | 40 | 90 | $4,275,000 | $940,500 |
Oracle would discount those purchases, but you would be negotiating after the ceiling is fixed, with deployments already running. The full count costs nothing extra, because the ULA fee has already paid for it.
How do you turn cores into processors?
Multiply the physical cores by the factor in Oracle's processor core factor table. Current Intel Xeon and AMD EPYC chips carry a factor of 0.5, so a two socket server with 16 cores per socket has 32 cores and counts as 16 processors. Our core factor guide covers the exceptions.
How do you build a certification count you can stand behind?
Run the count as a project on your own tooling and calendar, starting about twelve months before the end date. Nothing in a typical certification clause obliges you to run Oracle's scripts to produce your own declaration. Discovery has to cover every subnet, because Oracle licenses development, test, QA and training on the same basis as production.
Record against every server which counting test it passes, which legal entity owns it, and whether it runs on premises or in an authorized cloud. Those three fields let you rebuild any line of the declaration later.
Which tools show what is installed and running?
Use sources that already exist on your servers and consoles. Treat Oracle Enterprise Manager and the CMDB as cross checks only, since neither sees servers that were never registered.
- Installed software. The Oracle central inventory on each host (inventory.xml under oraInventory/ContentsXML) lists every Oracle home, including dormant ones.
- Running instances. On Linux and UNIX, each running database has an ora_pmon process; on Windows, look for the OracleService entries.
- Options and packs. DBA_FEATURE_USAGE_STATISTICS shows which database options have been used, which matters if the ULA covers options.
- Hardware. lscpu on physical hosts, and the vCenter host and cluster inventory for VMware, give sockets, cores and cluster membership.
- Cloud. Instance inventories and billing exports from each provider show vCPU counts over time, which you need for any trailing average.
When should each part of the work happen?
| When | What to do |
|---|---|
| 12 months before | Extract the six clause elements. Get the legal entity list. Start discovery across every subnet, non production included. |
| 6 months before | Produce the first full count under the clause's test. Decide which deployments you need before the ceiling is fixed. |
| 3 months before | Close the entity and cloud questions with counsel. Draft the letter and confirm the named signatory. |
| 1 month before | Rerun discovery to catch changes. Agree the evidence snapshot you will take on the certification date. |
| Certification date | Capture the snapshot. Use this one date everywhere in the letter. |
| Inside the window | Sign, deliver by the method the contract specifies, and follow up until the countersigned schedule is back. |
Why we advise against a last minute deployment push
The usual ULA advice is to deploy as much as you can in the last months so the certified number rises. We think it is mostly wrong on current contracts. Where cloud was capped at a trailing average, capacity added in the final months moved the certified number by a few percent at most.
On premises servers bought only to lift the count carry hardware and hosting costs, and Oracle is likely to question deployments with no workload behind them. Decide real deployments early in the final year, as our ULA renewal tactics describe, and spend the last months finding what is already running and uncounted.
What should an Oracle ULA certification letter contain?
A certification letter that holds up is plain and specific. It goes out on the contracting entity's letterhead, signed by the officer the clause names, and is delivered by the method the contract specifies. It should contain these parts.
- The reference. The ordering document number and the ULA term dates, so there is no doubt which contract the quantities certify.
- The date. The certification date, stated once and used consistently for every quantity.
- The products. Each ULA product by its full Oracle name, never an internal abbreviation, with the license metric beside each quantity.
- The scope statement. A sentence confirming the quantities reflect programs installed and running as of that date, within the licensed entity scope.
- The countersignature request. A request that Oracle acknowledge and countersign the quantity schedule.
Why ask Oracle to countersign the quantity schedule?
Without it, your only evidence of entitlement three years later is a letter you wrote yourself. The request costs one sentence while your records are at their most complete, and it heads off a dispute when you are most exposed, usually in a later audit or support renewal.
Keep the evidence pack behind each line of the schedule: discovery exports, the entity reconciliation, the cloud calculation and counsel's sign off. If Oracle questions a quantity, you answer from the file.
What will Oracle's account team say, and how should you reply?
Account teams often steer the conversation toward a lower count or toward a renewal. These are the lines we hear most, with the reply that fits each.
- "Send us the numbers and we will validate them with our scripts." Your clause asks for a certification signed by an officer. Offer a per product evidence summary, and route any formal verification request through the audit clause of your agreement.
- "Renewing is simpler than certifying." A renewal still closes the expiring term. Ask for the renewal price next to the certify and exit option, and compare both over five years.
- "The company you acquired is not covered." Point to the entity definition and its acquisition language. If the wording reaches the subsidiary, its deployments count. If it does not, raise it before the end date, while an amendment is still possible.
- "We will confirm receipt of your letter." Receipt proves delivery. Ask for the quantity schedule to be countersigned.
What certification terms should you negotiate into a new or renewed ULA?
If you are signing or renewing a ULA, the certification clause is the one to negotiate hardest, because it fixes the result of the whole term. Ask for these terms in the ordering document.
- A longer window, in business days. 60 or 90 days with a clear trigger gives time to correct reconciliation errors.
- An "installed" counting test. Standby, disaster recovery and idle test servers then count toward your entitlement.
- Acquisition language. Entities acquired during the term above an ownership threshold you set are in scope without a separate amendment.
- Cloud counted on the certification date. Authorized cloud deployments count at their actual size on that date.
- A countersignature obligation. Oracle confirms the certified quantities in writing within a stated period after delivery.
- A capped failure consequence. A late letter reverts to prior entitlement after a cure notice, never to zero.
What have we seen in recent ULA certifications?
Across the 30 to 40 Oracle ULA certifications I ran or reviewed in 2024 and 2025, the letters themselves were mostly sound. The errors came from the count behind them.
- No countersignature. Roughly four in five declarations went out without any request for a countersigned quantity schedule.
- Non production left out. In more than half of the engagements, the first draft missed non production, usually because discovery had run against production subnets only.
- Late cloud capacity. Where the trailing average applied, capacity added in the final months barely changed the result.
The declaration itself was rarely the problem. The preparation behind it was.
Both directions of error carry a cost. An undercount turns deployments you could have certified for free into purchases later, made after the ceiling is fixed. An overcount gains you nothing and puts an officer's signature on quantities your evidence cannot support. That invites Oracle to test every other line of the letter.
The number to aim for is the highest one your evidence supports: non production included, entity scope fully reached, counted under your clause's own test, and countersigned. What happens to that entitlement after certification is covered in our exit strategy guide.
What to do next
- Pull the ordering document. Extract the six clause elements, because the window, the counting test and the failure consequence shape the whole project.
- Run discovery across every subnet. Include development, test, QA and training, since all of them count.
- Reconcile the entity scope. Check every acquisition against the definition, because acquired companies count only where the language reaches them.
- Read your own cloud clause. Settle whether it excludes cloud or averages it before anyone plans a final month deployment push.
- Draft the letter early. Confirm the signatory, the letterhead, the date and the delivery method with counsel.
- Request the countersigned quantity schedule. It turns your letter into evidence. Our Oracle practice runs certifications with you.
Frequently asked questions
Is Oracle ULA certification an audit?
No. It is a declaration signed by an authorized officer of your company, and Oracle turns the quantities into perpetual licenses. Oracle may ask questions about the letter, but the count, the evidence and the timing are yours to set within the clause.
How long do you have to certify an Oracle ULA?
As long as your clause says. Thirty days after the end date is the most common window, and a meaningful minority of contracts allow 60 or 90. Check whether the days are calendar or business days and what event starts the clock, since both vary between ordering documents.
Does non production count in ULA certification?
Yes. Development, test, QA and training environments need licenses just as production does, so they belong in the certified quantity. In more than half of our engagements they were missing from the first draft, usually because discovery never reached the non production subnets.
Can cloud deployments be certified in a ULA?
Only on the terms of your own contract. Many post 2019 ordering documents exclude authorized cloud environments or limit them to a trailing average of past usage, while some older ones say nothing. An averaged figure hardly responds to late additions, so plan cloud growth well ahead of the end date.
What is a countersigned quantity schedule and why does it matter?
It is Oracle's signed acknowledgment of the quantities you certified. Without one, a later audit or support dispute starts from a letter you wrote yourself. Put the request in the certification letter and follow up until Oracle returns it.
Should you certify high or low on a ULA?
Neither. Certify the highest number your evidence supports. Leaving servers out converts free deployments into later purchases at list prices. Overstating gains nothing, since support on a standard ULA does not rise or fall with the count, and it exposes the officer who signed to a challenge on every line.
Who should sign an Oracle ULA certification?
The officer your clause names, signing for the contracting entity on that entity's letterhead. Check the exact title in the ordering document before the letter is drafted, because a letter signed by the wrong person or for the wrong entity gives Oracle grounds to challenge it.
Can Oracle audit you after ULA certification?
Yes. Certification ends the unlimited term but leaves the audit clause in your master agreement in place. After it, the certified quantities are the entitlement Oracle measures you against, which is why the countersigned schedule and your evidence pack should be kept with the contract.