Contents
Key takeawaysWhy Oracle pushes backWhat the pressure looks likeWhy starting early paysCertifying under pressureWhat we have seenWhat to do nextFAQOracle earns more from a renewal than from a certification, so a compliance question late in the term is predictable. Buyers who count their own deployments 9 to 12 months out answer it from evidence and certify more.
- The pressure follows the calendar. Oracle raised a compliance question or proposed a review in roughly 6 in 10 of the exits we supported, almost always in the final two quarters.
- Certification caps Oracle's revenue. It converts unlimited use into a fixed perpetual count, while a renewal extends and usually grows the support relationship.
- Early counts come in higher. Clients who started early certified 12 to 22 percent more than their own first internal estimate.
- Late starts certify low for good. Buyers who began inside 90 days of the end date left perpetual entitlement behind, and the number cannot be revised afterwards.
- Internal counts miss deployments. An independent sweep found eligible deployments the internal team had missed in four of five engagements.
- Keep the renewal on its own track. Answer compliance questions in writing from your evidence pack and decline to price a second term until your baseline is final.
Why does Oracle push back when you plan to certify an Oracle ULA?
Oracle earns more from a renewal than from a certification. Certifying ends your unlimited right and converts what you have deployed into a fixed perpetual count, which caps the support relationship. A renewal extends it and usually grows it, so pressure to renew in the last months of a term is a commercial response to the calendar.
A compliance question in the final two quarters says more about where you are in the term than about the state of your servers. In roughly 6 in 10 of the exits we supported, Oracle raised a compliance question or proposed a review, and almost every one landed inside those last two quarters.
What does certification end, and what does a renewal keep?
The two outcomes move Oracle's revenue in opposite directions. The table sets out what each one does to your position and to Oracle's, which explains why the account team's interest peaks just before the end date.
| Question | If you certify | If you renew |
|---|---|---|
| What you hold afterwards | A fixed perpetual license count for each ULA product | Another unlimited term for the listed products |
| What happens to support | Continues on the certified licenses, now capped in scope | Continues and is usually repriced upward in the new agreement |
| Future growth | Every processor above the certified count is a new purchase | Covered until the next end date, then the same decision returns |
| Who sets the number | You, through a declaration an officer signs | No number is fixed until the next certification |
None of this makes renewal the wrong choice. For a business still growing its Oracle footprint fast, another term can be the cheaper path. Make that choice on your own numbers; our exit strategy guide shows how to price both options.
How to Negotiate an Oracle ULA: No Price List, Just Your Business Case
What does Oracle's retention pressure look like before a ULA ends?
It usually arrives as one of four things, and each has a plain answer if you already hold your own count. The pattern below comes from the certifications we supported, and it repeats closely enough that you can plan for it the day you decide to certify.
| What arrives | When | How to answer |
|---|---|---|
| A compliance question | Final two quarters | From your own evidence, in writing, on your timeline |
| A proposed review | Alongside the renewal pitch | Keep it separate from the renewal conversation, and say so explicitly |
| An offer to count for you | Whenever your own count is running late | Decline; the declaration is yours to make |
| A renewal quote | Before your count is final | Decline to price it until your baseline is done |
Why does the timing repeat so consistently?
Certification replaces an unlimited right with a fixed number and caps a growing support relationship, so uncertainty is worth most to the seller just before the end date. A buyer without a finished count cannot tell whether a question is material, size the exposure or separate a routine inquiry from a real finding.
Doubt of that kind has an obvious way out, and the way out on offer is a renewal, which makes the question disappear. The buyer who already holds a documented count faces the same letter as a fact checking exercise. Your protection is having the number first, so the question has something to be checked against.
What will the account team say, and what should you say back?
- "We would like our licensing team to run a review before you certify." Reply that certification is your declaration under the ULA clause. Any review Oracle wants is a separate matter under the audit clause of your master agreement, with its own notice terms, and you will not merge the two.
- "We have concerns about usage of options outside the agreement." Ask for the host names, products and evidence in writing. Products outside the ULA list are a separate licensing question and do not change what you certify for the listed products.
- "Our scripts would make certification easier for you." Say you run the measurement yourselves, and Oracle will receive the declaration and whatever supporting detail the clause requires.
- "A renewal now removes all of this risk, and we can hold today's price." Say you will review a renewal quote once your baseline is final, and give a date.
- "Your certified number looks high and we need to validate it." Send the evidence pack for the lines in question and ask Oracle to name any host it believes is counted wrongly. That keeps the exchange on specific servers.
Oracle ULA Decision Guide
Certification, exit and renewal compared, with the steps and timing for each.
Get the white paper →Why does starting early raise the number you certify?
Counts improve with time. Clients who started early certified on average 12 to 22 percent more than their own first internal estimate, because the first pass always misses deployments. Buyers who began inside 90 days of the end date certified low, and the number cannot be revised once the letter is filed.
Those missing processors are perpetual entitlement you paid for during the term through the ULA fee. A rushed count hands them back to Oracle for nothing, and if the workloads are still running, you buy them again later at a price Oracle sets.
Where do internal counts miss deployments?
An independent discovery sweep found eligible deployments the internal team had missed in 4 in 5 of our engagements. The misses cluster in the same places:
- Virtual environments. VMware clusters where Oracle workloads moved between hosts, and hosts that were never tied back to the Oracle inventory. Our note on virtualized Oracle licensing covers how Oracle counts them.
- Forgotten environments. Disaster recovery copies, training systems, project servers left behind after a migration, and subsidiaries whose IT sits outside the central team.
- Uncatalogued option usage. Database options and packs that were switched on by default or by a single project and never recorded, which matters when the ULA covers them.
- Cloud instances. Workloads in authorized cloud environments, which count or not depending on your clause and on the vCPU counting rules.
What is the preparation premium worth in dollars?
Take a hypothetical ULA covering Database Enterprise Edition, where the first internal estimate is 200 processors. If preparation adds what it added on average in our engagements, the certified count lands between 224 and 244. Priced at Oracle's published list of $47,500 per processor, with $10,450 a year of support, the difference looks like this.
| Count | Processors certified | Processors added | List license value of the addition | List support on the addition, per year |
|---|---|---|---|---|
| Rushed count, first estimate | 200 | 0 | $0 | $0 |
| Prepared count, low end (12 percent) | 224 | 24 | $1,140,000 | $250,800 |
| Prepared count, high end (22 percent) | 244 | 44 | $2,090,000 | $459,800 |
On a standard ULA the support bill does not grow with the certified count, so the extra processors cost nothing at certification. The value shows up later, as purchases you never have to make when those workloads keep running or grow. Oracle discounts real purchases, so the list figures overstate the cash at risk, but they show its scale.
Processor counts depend on the core factor table, so convert cores before you compare.
How do you certify cleanly while Oracle raises compliance questions?
Do the count yourself, early, on the contract metric, and keep the renewal talks on a separate track. These six steps cover it:
- Start 9 to 12 months out. No compliance question can then arrive before you hold your own number, and no deadline can force a rushed count.
- Run your own measurement across physical, virtual and cloud hosts, and decline offers to be counted, because the declaration is yours and so is the evidence behind it.
- Commission an independent sweep to find what the internal pass missed, typically in virtual environments and uncatalogued option usage.
- Count on the contract metric, processor or named user as your signed agreement defines it, and ignore the metric anyone remembers from the last project.
- Keep the count complete and supportable. Include every workload that is really deployed and nothing merely theoretical, following the production reality standard.
- Separate the renewal conversation from the compliance conversation in writing, and decline to price a second term until the baseline is finished.
Should you accept a review early to show Oracle good faith?
A common piece of advice says cooperating with an Oracle review before you certify keeps the relationship smooth and avoids a dispute later. We see it differently. A review run before your own count finishes gives Oracle the first number, measured on its reading of the contract, at the moment you are least able to question it.
The better course is to finish and document your count, file the certification, and then answer specific questions from your evidence. Cooperation is still possible, and it is far cheaper once you hold the facts. If a formal audit notice follows, handle it under the audit clause on its own timetable, apart from any renewal.
What should the evidence pack behind each number contain?
- The discovery output for every host, with the date it was captured.
- The reconciliation between Oracle's measurement script output and your own tooling, with every difference explained.
- The hardware detail behind each processor figure: sockets, cores, core factor and cluster membership.
- The legal entity that owns each server, checked against the entity definition in the ULA.
- A short note for any server you excluded, stating which contract term excludes it.
The declaration mechanics, including the letter and who signs it, are in our certification guide. If you are already inside the final quarter, the 90 day checklist sets the order of work.
Keep the pack after you file. It records what ran on the certification date, which makes it the best audit defense you will have in the years after the ULA ends.
A compliance question sent to a buyer who already holds a documented count becomes correspondence, and a renewal quote becomes a comparison.
What have we seen in recent Oracle ULA certifications?
Across the 30 to 40 Oracle ULA certifications we supported from 2024 to 2026, the gap between a rushed count and a prepared one was wide. The compliance questions landed hardest on buyers who had no number of their own, because they could not tell a routine query from a real finding.
Two other patterns held. Late starters certified low and could not go back, and the deployments missed internally were rarely exotic: they sat in the virtual clusters, forgotten systems and option usage described above. The mistakes below account for most of the lost value.
Which mistakes cost buyers the most?
- Treating the compliance question as a verdict. Teams pause certification work to respond, lose weeks and end up short of time. Answer from your evidence and keep the count moving.
- Asking for a renewal quote as a fallback. Once a quote is on the table before your count is final, the conversation shifts to the price of renewing and away from what you own.
- Letting Oracle's tooling produce the first number. Whatever number appears first sets expectations, and correcting it later takes evidence you should have gathered anyway.
- Counting on the wrong metric. Mixing processor and named user figures, or using an old metric from a previous agreement, invites a challenge on lines that were otherwise sound.
- Finishing discovery with no time to reconcile. Raw script output without reconciliation is hard to stand behind if Oracle questions a single host.
When should each part of the work happen?
| Time before the end date | What to do | Why then |
|---|---|---|
| 12 months | Read the certification clause, name an owner, secure executive sponsorship | Leaves room for discovery, a sweep and reconciliation |
| 9 to 12 months | Run discovery across physical, virtual and cloud hosts | Your count exists before any compliance question can arrive |
| 6 months | Commission the independent sweep and close the gaps it finds | The final two quarters start here, and so does the pressure |
| 3 months | Freeze the evidence pack and draft the declaration | Inside 90 days there is no time left to find what was missed |
| 1 month to the end date | Confirm what is deployed on the end date, line up the officer's signature, and file within the window your clause sets | The count reflects what runs on the end date, not what ran months earlier |
What to do next
- Put certification on the calendar. Schedule it 9 to 12 months before the end date, with a named owner and executive sponsorship.
- Run discovery. Cover physical, virtual and cloud hosts, and reconcile the Oracle script output against your own tooling.
- Commission an independent sweep. Find the deployments the internal pass missed while the window is still open.
- Assemble the evidence pack. Document every number on the metric your signed agreement defines.
- Answer questions in writing. Reply to any compliance question from that pack, separately from the renewal conversation.
- Get help with the count if you need it. Our Oracle practice runs the discovery and the declaration with you, and the wider library sits in the Oracle knowledge hub.
Frequently asked questions
Why would Oracle discourage ULA certification?
Because a renewal is worth more to Oracle than an exit. Certification ends the unlimited right and fixes a perpetual count, so pushback near the end date is a commercial response to the calendar. It tells you little about whether anything is wrong with your deployments.
What form does Oracle's pressure usually take?
Most often a compliance question from the account team or a proposed review, nearly always in the last two quarters. It tends to come paired with a renewal offer, which is why it helps to answer the two in separate letters and on separate dates.
How much does starting early change the certified count?
Enough to matter in dollars. On our averages, early preparation turns a 200 processor first estimate into 224 to 244 certified processors. The extra months go on finding what the first pass missed and reconciling it, which a team starting in the last quarter cannot fit in.
Does an internal count find every Oracle deployment?
Rarely. Internal inventories are built for operations, so they miss systems outside daily operations: disaster recovery and training systems, servers owned by subsidiaries, and database options switched on by one project and never recorded. An independent sweep exists to find those.
Who should measure the deployments for a ULA certification?
You should. The declaration is signed by your officer, so the measurement behind it should be yours too. Running Oracle's measurement scripts yourself is fine; handing the count to Oracle's licensing team means the first number on the table is theirs.
What makes a ULA certification hard to challenge?
A count on the metric your signed agreement defines, processor or named user, with discovery output behind every line and a structured declaration. When Oracle queries a line, you send the evidence for that host rather than argue about the total, and a single query stays a single query.
When should ULA certification work start?
Nine to twelve months before the term ends. Starting then means any compliance question raised in the final quarters reaches a team that already holds its own number, and there is time for an independent sweep before the evidence pack is frozen.
Does a compliance question mean Oracle is auditing us?
Not by itself. A question from the account team is correspondence. A formal audit starts with written notice under the audit clause of your master agreement, and it runs on its own timetable, separate from the certification and from any renewal talks.