The working rule: certify when the deployment curve has flattened and the count you can lock in covers the foreseeable future; renew only when genuine growth ahead would outrun that count. Which path is actually available, though, is decided 12–24 months earlier — an organisation that has not built a verified deployment inventory by the final year of the term has, in practice, already chosen renewal, whatever it intended.
Published 31 October 2025 · Last reviewed 24 November 2025
Every fixed-term Oracle ULA ends the same way: the unlimited deployment window closes, and the customer either certifies — counts every in-scope deployment, declares the totals to Oracle, and converts them into a fixed grant of perpetual licenses — or renews, paying a new fee for another unlimited term. There is no third path; letting the term lapse without certifying simply means an uncounted estate with no unlimited cover, which is the worst available outcome.
The fork looks symmetric on paper and is asymmetric in practice. Certification is an operational project with a contractual deadline: the count must be accurate, defensible, and reconciled against scope language written years earlier. Renewal is a commercial transaction that can be closed in a meeting. That asymmetry is why the renewal path exerts a steady gravitational pull — it is always easier this quarter — and why the certification decision is really a preparation decision made a year or two before the term ends.
This guide is general information about Oracle commercial mechanics, not legal advice; ULA terms are individually drafted and your contract governs every counting question discussed here. It names no firms; the firm directory lists Oracle-capable advisors with balanced pros and cons, listed, not ranked.
Certification converts usage into entitlement: the quantities declared at term end become the perpetual license position the organisation owns from that day forward. Three mechanics decide how much value the conversion captures.
The inventory is the asset. Everything in scope and deployed counts; everything missed is unlicensed the moment the term ends. A defensible count means tooling-based discovery across every environment — physical, virtualized, containerized, cloud — reconciled against the contract's entity, territory and product-list language. Virtualized estates carry a known hazard: Oracle's position on soft partitioning means deployments on shared clusters can be counted far more broadly than the workloads themselves suggest, and the counting position taken at certification should be documented against the contract rather than assumed.
Cloud counting is contract-specific. Whether public-cloud deployments count toward certification, and on what rule, varies by agreement vintage. Some ULAs exclude public cloud from the count; many later agreements admit AWS and Azure deployments under an averaging mechanic — commonly the average across the final 12 months of the term rather than a point-in-time count — while OCI deployments are treated more generously under Oracle's own counting rules. Oracle's published cloud-counting policy has been revised repeatedly; the language in the order form, not the policy of the day, is what a buyer should rely on, and verifying it is step one of any certification plan.
The declaration is senior and final. The certification letter is typically signed at officer level, and the numbers in it become the license position an ordinary audit later tests. Certification is not itself an audit — but the audit clause survives in the perpetual licenses, so the count should be built to audit standard: evidence retained, counting positions documented, the reconciliation clean. Organisations that treat certification as a formality build, in effect, an unverified effective license position and then bet the estate on it.
One legitimate lever deserves naming: deployment before the count. Capacity deployed in-scope during the term counts, whether or not it is heavily used yet. Aligning planned deployments so they land inside the window is standard, contractually contemplated practice — it is what the unlimited fee bought — though it must stay inside scope language, and manufactured deployments with no operational reality invite challenge.
Renewal buys another unlimited window. For an estate with real growth ahead — a consolidation migrating workloads onto Oracle, an acquisition integration, a platform expansion — that window can be worth more than the license count certification would lock today. The renewal conversation is also a genuine negotiation point: product lists can be pruned or extended, scope language modernized (cloud counting above all), and support terms revisited.
Three things to see clearly before signing, all stated factually. First, the renewal fee re-prices the relationship at the moment the vendor has maximum information about your dependence — Oracle typically opens the conversation a few months before expiry, often alongside OCI or broader-agreement proposals, and the opening frame favors continuation. Second, each renewal generally grows the support base, and the support stream compounds across terms in a way single-term comparisons hide. Third, a renewal does not remove the certification problem; it defers it to a date when the estate — and therefore the count, and the stakes — will be larger. Renewing by default, because no count exists, pays a term fee to postpone a project that only gets harder.
The strongest renewal negotiations are run from a completed shadow count: knowing precisely what you would certify today converts the renewal from a hostage negotiation into a priced comparison. That is the central irony of the fork — the certification work is worth doing even when the answer turns out to be renewal, because it is the only thing that makes the renewal price honest. Running that comparison is the core of an independent Oracle renewal engagement.
| DIMENSION | CERTIFY OUT | RENEW |
|---|---|---|
| What you get | A fixed perpetual license count equal to the verified deployment position | Another unlimited term for the negotiated product list |
| New money | No new license fee; support continues on the existing base | A new term fee, priced at the moment of maximum vendor information |
| Growth after the event | Requires new purchases; the certified count is the ceiling | Unlimited within scope for the new term |
| Operational burden | High: verified inventory, counting positions, officer-level declaration | Low at signature; the counting problem is deferred, not removed |
| Risk profile | Undercounting becomes post-term compliance exposure; count must survive audit scrutiny | Support base compounds; dependence deepens; the next fork arrives with higher stakes |
| Leverage dynamics | Strongest with an early, verified count; declaration is yours to make | Strongest with a completed shadow count proving you can walk |
| Preparation clock | 12–24 months for inventory, counting positions and remediation | Same clock, honestly run — a renewal negotiated without a count is negotiated blind |
The last row is the page's argument in miniature: both paths are won or lost on the same preparation, started on the same early clock. The fork is not certify versus renew so much as prepared versus unprepared.
Starting the count in the final quarter. The inventory, the counting positions and the remediation each take quarters, not weeks. A late start forecloses certification and converts the renewal into the only option — at a price that reflects it.
Discovering the cloud clause at certification eve. Whether and how AWS, Azure and OCI deployments count is settled by contract language most organisations have not read since signature. Averaging mechanics in particular reshape strategy: a final-year cloud migration counts very differently under a 365-day average than under a point-in-time rule.
Certifying an unverified number. A count assembled from spreadsheets and good intentions becomes a liability the day it is declared. The certification inherits the audit clause; build it to audit standard or expect to defend it later without the evidence.
Ignoring out-of-scope usage during the term. Unlimited cover applies to the listed products only. Options, packs and products outside the list accumulate ordinary compliance exposure throughout the term — and surface at exactly the moment the relationship is being repriced.
Renewing to avoid the project. The most common path, and the most quietly expensive: a term fee paid to defer a count that grows with the estate, while the support base compounds beneath it.
Negotiating either path alone against a practiced counterparty. Oracle's team runs this fork weekly; most buyers face it once or twice a decade. Independent support on the count, the counting positions and the negotiation is the standard counter — and choosing that partner is its own decision, covered in its own guide.
The structure this fork lives inside →
The metrics a certification lands on →
What certified licenses are worth in the cloud →
How to pick the firm for this work →
Firms that run the end-of-term fork →
Every field guide on the site →
Certification is the contractual exit at the end of a ULA term: you count every in-scope deployment as of the certification date, declare the totals to Oracle in a formal certification letter (typically signed by a senior officer), and those quantities convert into fixed perpetual licenses you own from then on. Deployment growth after certification requires new licenses; the unlimited period is over.
Twelve months before term end at minimum; estates with significant virtualization or public cloud footprints generally need 18–24 months. The work — building a verified deployment inventory, resolving counting questions against the contract, deploying entitled-but-unused capacity where the strategy calls for it — takes multiple quarters, and a certification that begins at the vendor’s first renewal call has already surrendered most of its leverage.
It depends entirely on your contract. Some ULAs exclude public cloud from certification counts; many more recent agreements count AWS and Azure deployments under an averaging mechanic, such as the average over the final 12 months of the term, rather than the point-in-time count used on-premises; OCI deployments are generally treated more generously under Oracle’s own counting rules. Because Oracle’s cloud counting policies have been revised repeatedly, the contract language at signature — not the policy of the day — is what should govern, and checking that language is one of the first steps of certification planning.
Anything deployed but not certified is unlicensed the moment the ULA ends — discovered later, it becomes a compliance finding in an ordinary audit, with no unlimited agreement left to absorb it. Undercounting is the single most expensive certification error, which is why the deployment inventory needs independent verification rather than a hurried scrape in the final quarter.
Certification itself is a declaration, not an audit, but Oracle can review the certification and can audit the estate afterwards under the standard audit clause that survives in the perpetual licenses. A defensible certification therefore looks like an audit response prepared in advance: tooling-based evidence, counting positions documented against contract language, and a clean reconciliation between inventory and the certified numbers.
Yes — when genuine deployment growth lies ahead. If the next three years hold a migration, an acquisition integration, or platform growth that would outrun the license count you could certify today, a renewal can price that growth more efficiently than buying licenses incrementally. The renewal is the wrong default, though: renewing because certification preparation never happened pays a term fee to postpone a count that only gets larger.
Timing the clock, building the count and pricing the fork is exactly what an Oracle licensing advisor is for. The directory lists the firms that do this work, with balanced pros and cons, listed, not ranked.
Tell us the vendor, the service you need and where things stand, and we will route your brief to firms that genuinely cover that combination. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.