Contents
Key takeawaysWhat you own after exitCost above the ceilingWhy support does not fallMaximizing the certified countStaying under the ceilingWhat Oracle will sayWhat we saw, 2024 to 2026Exit timelineWhat to do nextFAQCertifying a ULA swaps unlimited use for a fixed perpetual count per product, with support unchanged and list price for every unit above the line. Most costly mistakes happen in the eighteen months after the exit.
- Exit sets a ceiling. You keep perpetual licenses at the certified quantity and keep paying support on them; nothing about the exit itself lowers cost.
- Growth above the line is a full price purchase. Deployment was free during the term, and the first processor over the certified number is bought from list when a project needs it.
- Support holds. It follows the licenses in the support contract, and Oracle's policies reprice the rest if you terminate part of an order.
- Pull headroom forward. Roughly 20 percent of forecast growth, deployed before the date, costs nothing and stays in the certified count for good.
- Certification opens alternatives. Third party support and real reductions become possible only once you hold perpetual licenses instead of a term right.
- A register prevents drift. Customers who published the certified quantity and checked it in change control did not cross the ceiling; those without one drifted past it one project at a time.
An Oracle ULA exit strategy has to cover the years after the certification date, because that is when most of the cost arrives. The declaration mechanics are in our certification guide, and the case for signing a second ULA is in the renewal tactics.
What do you own after an Oracle ULA exit?
You own a fixed number of perpetual licenses for each product in the ULA, equal to the quantity you certified. You also keep a support contract on those licenses, and every unit of growth above that number is now a separate purchase.
That certified quantity replaces unlimited, product by product, for good. It becomes the figure Oracle measures you against in any later review, and the figure your architects have to design within.
| Dimension | Inside the ULA term | After certification |
|---|---|---|
| Deployment | Unlimited for the named products | Capped at the certified quantity |
| Cost of growth | Zero at the margin | Full price, negotiated one purchase at a time |
| Support | Fixed annual stream through the term | Calculated on licenses held; it does not fall on its own |
| Alternatives | None, because you hold a term right | Third party support becomes possible |
| Audit exposure | Bounded by the unlimited right | Live again, measured against the certified count |
Oracle is still your vendor after the exit
An exit ends the unlimited grant, and the rest of the relationship carries on. Oracle still holds your support contract, and the audit clause in your license agreement outlives the ULA term.
What changes is that cost now follows quantity. Every processor above the certified line is a purchase, and every reduction below it runs into Oracle's support policies. Any project that adds Oracle capacity has become a licensing decision, even when the project team does not see it that way.
How to Negotiate an Oracle ULA: No Price List, Just Your Business Case
Why does the first processor above the certified count cost so much?
It is a full price purchase from Oracle's list, and the day before the certification date the same processor cost nothing. On the last day of the term, an extra processor of Oracle Database sits inside the unlimited right, and any engineer with a change ticket can deploy it.
A day later that processor is a separate order, negotiated on its own at whatever moment a project needs it. You have little room to bargain because the project is waiting. The hardware and the software are the same on both days; only the contract changed, and with it your cost per unit of growth.
A worked example: one new database cluster, before and after the date
Say your roadmap needs a two host database cluster, each host with 32 Intel Xeon cores. Oracle's core factor for Xeon is 0.5, so 64 cores become 32 processor licenses. The cluster runs Database Enterprise Edition with Real Application Clusters, both included in your ULA. The core factor table explains the conversion.
| Item | List price per processor | Deployed inside the term | Bought after certification |
|---|---|---|---|
| Database Enterprise Edition license | $47,500 | $0 | $1,520,000 |
| Real Application Clusters license | $23,000 | $0 | $736,000 |
| Total license | $70,500 | $0 | $2,256,000 |
| Annual support (EE $10,450, RAC $5,060) | $15,510 | No increase; the ULA support stream covers it | $496,320 a year, rising with renewal adjustments |
A negotiated discount would reduce the right hand column, but you will be negotiating it with a project deadline working against you. The left hand column also adds 32 processors to your certified count, which stay yours permanently.
How much headroom should you pull forward before certifying?
Roughly 20 percent of forecast growth is the band we typically see justified. Pull forward capacity the roadmap already supports and deploy it inside the term, where it costs nothing. The same capacity prices at list the following week.
Buyers hesitate because it means deploying before the business asks. In the example above, 20 percent of a three year forecast of 160 processors is 32, the cluster in the table. Customers who did it bought years of headroom by resequencing a few projects, while the rest found the ceiling one purchase order at a time.
Oracle ULA Exit Strategy Paper
How to sequence the exit, set the certified count and control growth in the years after.
Get the white paper →Does Oracle support fall when a ULA ends?
No. Support after exit is calculated on the licenses in your support contract, and the ULA support stream carries over to the certified licenses. It does not drop because the unlimited right has ended. Nearly every buyer we worked with expected it to fall, and it held.
What happens if you terminate some certified licenses?
Reducing support means terminating licenses, and Oracle's technical support policies set the rules. You cannot leave part of a license set unsupported. If you terminate some licenses on an order, Oracle reprices support on the rest at current list support minus the standard discount.
The repriced amount cannot exceed what you paid before for the kept and terminated licenses together. It also cannot fall below what you paid for the licenses you keep. After a ULA, those rules often cancel out the saving you expected.
- Starting point. You certify 400 Database Enterprise Edition processors and pay $1,800,000 a year in support, about $4,500 per processor.
- The cut. You terminate 100 unused processors. The remaining 300 reprice at list support of $10,450 each, or $3,135,000 before the standard discount.
- The cap. That exceeds the $1,800,000 you paid before, so the bill stays at $1,800,000 unless the standard discount tops about 43 percent.
- The floor. The best possible result is $1,350,000, the share you already paid for the 300 you keep.
Why we disagree that exiting a ULA cuts the Oracle bill
A common line from advisors and internal sponsors is that leaving the ULA will save money once the unlimited fee is gone. We disagree. Once the ULA license fee is paid, the recurring cost is support, and in the exits we ran it continued at the same level on the certified licenses.
Model the first three years of support on the certified quantity, including what a partial termination would reprice. Present the exit as a way to stop paying for growth you may not need and to open other support options. Keep savings out of the business case unless you can show where they come from.
Why third party support only becomes possible after certification
While you hold a term right, there is nothing to move to another support provider. Once you hold perpetual licenses, third party support is a real option for the first time, and it is often the strongest argument for exiting instead of signing a second term you do not need.
Weigh it carefully. You lose Oracle patches and new releases for the programs you move. Coming back later costs 150 percent of the last annual support fee, prorated over the whole period support lapsed, under Oracle's policies. Two years away therefore costs about three years of support to return, as our note on dropping Oracle support and reinstatement explains.
How do you maximize the certified count before the date?
Count every deployment the contract allows you to count, product by product, and keep the evidence behind each number. A higher certified number is a higher permanent entitlement, and it is only yours to set before the date. After that, the quantity is fixed.
How to check your own deployment position
- Oracle's measurement scripts. Run the same collection scripts Oracle's audit team uses, on every server, before Oracle asks. Our script analysis explains what they capture.
- Feature usage. Query DBA_FEATURE_USAGE_STATISTICS on each database to see which options and packs are in use. Read our note on the feature usage report first.
- Virtualization inventory. Export host and cluster membership from vCenter or your hypervisor console. On VMware, Oracle's position is that every host a database can reach counts, which our VMware licensing guide covers.
- Hardware records. Match physical core counts and processor models from your CMDB to the core factor table.
Which deployments may not count toward certification?
Read the ULA ordering document for limits on where deployments count. Many older ULAs restrict counting to certain territories or exclude deployments in third party public clouds such as AWS or Azure. Our guide to ULA deployments on AWS covers that case, and the 90 day certification checklist sets out the order of work.
How do you stop crossing the certified ceiling after exit?
Publish the certified quantity as an internal register and enforce it through change control. In our exits, that one control separated the buyers who stayed under the ceiling from those who crossed it.
Drift comes from changes no one reviews as Oracle decisions: a new cluster, a disaster recovery environment, or databases moved onto bigger hosts. Each adds processors, and none of them looks like a license purchase to the change board that approves it. The register puts the licensing question in front of that board.
What the certified quantity register should hold
- Certified quantity per product and metric. Copied from the signed certification, with the product names exactly as Oracle lists them.
- Current deployment per product. Refreshed each quarter from the same scripts and inventory used for certification.
- Headroom remaining. The gap between the two, visible to architecture review.
- Change control trigger. Any change that adds hosts, cores or options to Oracle workloads needs a licensing sign off before approval.
- Owner. One named person in software asset management who answers for the number.
Keep the quarterly refreshes and the certification evidence together. If Oracle opens a review, they are the file you hand over, because the certified count is now the number you have to prove.
What will the Oracle account team say about your exit?
Expect the conversation to push toward renewal or toward a smaller certified number. These are lines we hear often, with replies that hold up.
- "Certification is risky; renew and avoid it." Reply that you have measured the deployment and know the count, and ask for the renewal quote in writing so you can compare it with the cost of the ceiling.
- "Those deployments cannot be included." Ask for the clause that excludes them, and compare it with the wording of your own ordering document.
- "We can extend the ULA if you add a cloud commitment." Ask for the extension and the cloud spend priced as separate lines, so you can see what each part costs and compare the extension with the headroom you can still deploy.
- "You are above the certified number; you need a new ULA." Price the shortfall as a normal purchase first, then decide whether a new agreement is justified. Our note on how Oracle tries to stop certification covers the pressure in more detail.
What have we seen in Oracle ULA exits from 2024 to 2026?
We ran or reviewed 30 to 40 Oracle ULA certifications and exits over that period. The costs clustered in the months after the event, and the expensive mistakes tended to surface within about eighteen months of the date.
- Support expected to fall. Nearly all buyers were surprised that the bill held, because it tracks the licenses held.
- Ceilings crossed within two years. A meaningful share of customers drifted past the certified count, always through a project that was never reviewed as a licensing decision, and always where no register made the line visible.
- Headroom left on the table. Capacity the roadmap justified was not pulled forward while it was free.
Treat the day after certification as the start of the project, because that is when the ceiling starts to cost money.
What should an Oracle ULA exit timeline look like?
Start a year before the certification date and keep going for two years after it. The table sets out the work by stage.
| When | What to do |
|---|---|
| 12 months before | Decide between exit and renewal. Read the ULA ordering document for certification terms, territory and cloud limits. |
| 6 months before | Run the measurement scripts and inventory. Pick the roadmap capacity worth pulling forward and schedule it. |
| 3 months before | Deploy the headroom. Model support for the first three years on the certified quantity. |
| 1 month before | Freeze the counts, assemble the evidence per product, and prepare the certification for signature. |
| First year after | Publish the register, wire it into change control, and price third party support. |
| Second year after | Refresh deployment against the ceiling each quarter and keep audit evidence current. |
What to do next
- Find the headroom. Identify the roadmap capacity worth pulling forward and deploy it before the certification date, while it is free.
- Set the count. Maximize and document the certified quantity product by product, with the evidence behind each number.
- Publish the register. Share the certified quantity internally and build the ceiling into change control and architecture review.
- Model support. Project the first three years realistically, including what a partial termination would reprice.
- Price the alternatives. Get third party support quotes now that they apply, and keep audit readiness live. Our Oracle practice runs the exit with you, and the Oracle knowledge hub holds the wider library.
Frequently asked questions
What do you own the day after Oracle ULA certification?
A fixed quantity of perpetual licenses for each certified product, a support contract on that quantity, and a ceiling above which every processor is a new purchase. The certification document is now your main entitlement record, so store the signed copy with the ordering document and the evidence behind each count.
Does the support bill fall when the ULA ends?
No. The annual support amount carries over to the certified licenses and continues with the usual renewal adjustments. The only way to shrink it is to terminate licenses, and Oracle's repricing rule often leaves the total unchanged after a ULA. Build the first three years of support into the exit budget at today's level.
Why is the first processor above the ceiling so expensive?
It is priced from the Oracle list, with Database Enterprise Edition at $47,500 per processor before options, and it is usually bought under a project deadline. Inside the term the same processor cost nothing. That gap between free and list, at a single date, drives the economics of every ULA exit.
How do you buy headroom before the certification date?
Deploy it inside the term. Take capacity the roadmap already supports for the next few years, such as planned clusters, disaster recovery or host refreshes, and build it before the date so it counts. Deployments made after the date do not count, however close to it they fall.
What does certification make possible?
Alternatives. With perpetual licenses you can move some or all programs to third party support, terminate licenses you no longer run, or plan a gradual move away from some Oracle products. None of that is available while you hold only a term right, which is why exit often beats a second ULA.
How quickly do customers cross the certified ceiling?
Within two years in a meaningful share of the exits we saw, usually through one project that no one flagged as an Oracle decision. The fix costs little: a published register of certified quantities, a quarterly deployment refresh, and a licensing check inside change control before new hosts or options go live.
Does the Oracle audit clause survive a ULA exit?
Yes. The audit rights sit in your license agreement, which outlives the unlimited grant, so Oracle can review your deployments in the years after exit. The difference is the yardstick: any review now measures you against the certified quantity, so keep the certification evidence and quarterly refreshes ready to show.
Should you exit the ULA or renew it?
Exit when forecast growth is modest and the certified count covers it with room to spare. Renew only when growth would clearly exceed what you can pull forward, and price that renewal against buying the shortfall as ordinary licenses. Either way, measure deployment first so the decision rests on your own count.