The Oracle ULA certification checklist: the five C's that decide what you keep
Certification is the single highest-stakes event in Oracle licensing — the day your unlimited-deployment rights convert into a fixed, perpetual grant. Get the sequence right and you keep everything you've deployed. Get it wrong and Oracle hands you a renewal you never needed. Here is the five-step checklist.
An Oracle Unlimited License Agreement gives you the right to deploy certain products without counting — for a fixed term, usually three years. Certification is the day that term ends and you convert what you've deployed into a permanent, perpetual entitlement. Everything you can legitimately count on that day, you keep forever. Everything you miss, you don't.
That asymmetry is why certification is worth preparing for like nothing else in your Oracle relationship. There are five steps to doing it well — the five C's — and the value is entirely in following them in order. Skip one, or run them out of sequence, and you either leave perpetual rights on the table or walk into a compliance gap that Oracle turns into a forced renewal.
01Contract review — the first C
Before you count anything, read what you actually signed. The Ordering Document, the Oracle Master Agreement and every amendment and annexure together define what you're allowed to certify — and the restrictions live in the detail, not the headline. A proper review settles, in writing, each of these:
- Language and definitions. Confirm the terminology is clear and consistent across documents — ambiguity here becomes Oracle's interpretation later.
- Product-by-product licensing policy. Understand the specific rules for each product in the ULA; they are not uniform.
- Usage rights and restrictions. Identify any special grants or limits attached to individual products.
- Deployment and certification restrictions. Look specifically for constraints on where you may deploy and what may be counted at certification — territory limits, entity limits, cloud caveats.
- Support cost and term. Know the support obligations that survive certification, so the exit doesn't hand you an unexpected annuity.
- Non-contractual and future obligations. Weigh industry standards and any forward commitments against your current deployment plan.
Everything that follows is measured against this reading. If you count first and read later, you count against the wrong rules.
02Count the deployment — the second C
The second C is a comprehensive, enterprise-wide discovery. Not a sample, not the environments you remember — every place an Oracle product runs. Accurate counting is what turns unlimited rights into a defensible number, and it has to:
- Encompass every deployment — on-premises, virtualised, and every cloud environment, including the ones spun up outside central IT.
- Catalogue every product, version and configuration so the declaration reflects reality rather than the last known inventory.
- Verify entitlements against what the contract review established you're allowed to certify.
- Document non-standard configurations — the custom setups and edge cases that most affect the count.
- Assess your compliance posture from the findings, so you know before Oracle does where the gaps are.
03Comply: remediate and rebalance — the third C
Counting almost always surfaces a gap between what you've deployed and what you're strictly entitled to. The third C closes that gap on your terms, before you declare anything to Oracle. It has two distinct halves:
- Remediation — addressing non-compliance. Where actual usage exceeds your entitlements, build a plan to bring it back in line: right-size the deployment, or where genuinely needed, secure the licences to cover it. The point is that you resolve it deliberately, rather than Oracle finding it.
- Rebalancing — optimising the estate. Consolidate where you can, decommission unused software, and reallocate licences to where the business actually needs them — so the position you certify is both compliant and as strong as it legitimately can be.
This is also where deployment maximisation belongs: while the unlimited window is still open, deploy what you will genuinely use, so it counts toward the perpetual grant. Done after certification, that same growth costs you money. Done now, it's free.
04Count again — the fourth C
Remediation and rebalancing change the estate, so the pre-remediation count no longer describes it. The fourth C is a follow-up discovery that verifies the effect of everything you just did — confirming the gaps are closed, the optimisations landed, and the numbers you're about to certify are the numbers that are actually true today. Certifying against a stale count is how clean positions turn into disputes.
05Certify — the fifth C
With the estate reviewed, counted, remediated and re-counted, you can approach certification from strength. The process itself is a declaration and its defence:
| STEP | WHAT CERTIFICATION ACTUALLY INVOLVES |
|---|---|
| DECLARE | Submit a comprehensive declaration of all deployments — product inventory, deployment locations and usage metrics. |
| AUDIT | Oracle may verify the declaration through a licence audit; your counting has to be strong enough to withstand it. |
| REVIEW | Oracle reviews the documentation for accuracy and completeness — gaps invite questions. |
| INTERVIEW | Auditors may engage your team directly; consistent, prepared answers matter as much as the numbers. |
Do this on a well-prepared position and certification is confirmation, not confrontation. Do it on a rushed one and you invite exactly the audit and the forced-renewal pressure the whole exercise exists to avoid.
Certifying your ULA — and want it to hold?
Our ULA Certification engagement takes you through all five C's, then does what no publisher partner will: guarantee the certified position for three years. If Oracle challenges it, we defend it.
06Timelines: the mistake is starting late
WHERE ULA CERTIFICATIONS ARE WON OR LOST — ON THE CALENDAR
Start quarters ahead, not weeks. Deployment maximisation, remediation and a clean re-count all take time — and only work while the unlimited window is open.
Don't let Oracle's deadline decide. The renewal date is Oracle's lever. Begin early enough that certify-versus-renew stays your decision, made on your deployment trajectory.
Maximise before you count, not after. Everything you deploy inside the term counts toward the perpetual grant for free. The same deployment after certification is a purchase.
Document as you go. The evidence that defends a certification is far easier to assemble in real time than to reconstruct once Oracle asks.
We've helped more than 150 organisations certify their Oracle ULA, on estates from a couple of servers to tens of thousands. The ones that come out of it keeping everything they built almost always have one thing in common: they treated certification as a programme that starts early, not a form they file at the end. Run the five C's in order, on that timeline, and the day the term ends becomes the day you lock in everything you've earned.
07Straight answers to the questions we get most
ORACLE ULA CERTIFICATION — PLAIN-LANGUAGE FAQ
Should we certify or renew? It depends on trajectory. If growth in ULA-covered products has flattened, certification usually wins — you keep perpetual rights to everything deployed and stop paying for headroom. If real growth is ahead, a renegotiated ULA can make sense. Don't let the deadline choose.
Can Oracle audit our certification? Yes — after you declare, Oracle may review documentation, request evidence and interview your team. That's why the counting has to be defensible, not just submitted.
Remediation vs rebalancing — what's the difference? Remediation fixes non-compliance where usage exceeds entitlement. Rebalancing optimises the estate — consolidating, decommissioning and reallocating — so the certified position is both compliant and strong.
How early should we start? Quarters ahead. Maximisation, remediation and the re-count all need runway, and all depend on the unlimited window still being open.
What happens if we miss a deployment at certification? You lose the perpetual right to it. Re-acquiring it afterward is a purchase — which is exactly why the count, and the re-count, are worth doing thoroughly.