Start 12 to 18 months before the end date. Customers who start three months out almost always end up renewing.
ULA certification is how you exit an Oracle Unlimited License Agreement: you count what you have deployed, declare it to Oracle and receive perpetual licenses. We run the whole exit, and defend the certified position for three years.
36months of cover after exit: any challenge to the certified position is ours to answer
| Customers | Count |
|---|---|
| Advised on their ULAs | 125+ |
| Advised to certify | Nearly 100 |
| Forced by Oracle to renew | 0 |
After due diligence on each customer’s contracts, deployments and future licensing needs.
Exiting a ULA means certifying it: you count what is deployed, declare it to Oracle and receive perpetual licenses. These are the steps we follow, starting 12 to 18 months before the end date at the latest.
1. Review the contractThe ordering documents, the master agreement and every amendment, including the restrictions on deployment and on certification.
2. Count every deploymentDiscovery across the whole enterprise: known and unknown Oracle installations on premises, in virtual environments and in the cloud.
3. Build your license positionWhat is deployed, against what the contract allows you to certify.
4. RemediateFix any usage that exceeds what the contract allows, before Oracle finds it.
5. RebalanceConsolidate servers, decommission unused software and move licenses to where the business needs them.
6. Count againRepeat the discovery on the changed estate, so the number you declare is the number that is true.
7. Declare to OracleThe Oracle Server Worksheet, submitted with documentation you can defend.
8. Handle Oracle’s reviewClarification questions, and readiness for an audit of the declaration and for questions to your team.
9. Close with perpetual licensesOracle verifies the count and grants the licenses; you decide what to do about support.
For the longer version, read our Oracle ULA certification guide.
The biggest ULA problem is that Oracle has a vested interest in keeping customers inside the agreement. It makes significant money from ULAs, earns higher support fees when they renew, and loses the chance to keep you on Oracle when you certify. So the exit is made complex, obstacle-filled and potentially expensive. These are the problems we see most:
Non-complianceOracle knows many non-compliant customers will simply renew to avoid the hassle and expense of certifying.
Complex licensingOracle licensing is hard to read, even for experienced IT professionals.
Contract restrictionsEach ULA is customized and usually carries several restrictions. Misreading them can lead to heavy penalties or a forced renewal.
An audit at exitOracle may audit your environment to verify the declaration, and findings outside the ULA can follow.
Cloud deploymentsDeployments on public cloud are often excluded from the count (see below).
A rushed timelineCustomers who start three months out almost always end up renewing because they ran out of time.
A bank with more than 4,000 employees came to us eight months before its ULA end date. Oracle’s account team had proposed a three-year renewal at US$7.1M. We rebuilt the deployment picture against Oracle’s counting rules, maximized legitimate deployments in the remaining months and prepared the certification to audit standard. Oracle accepted the certification without dispute, 14 weeks after we started.
| As reviewed | Amount |
|---|---|
| Oracle ULA renewal, 3 years | US$7,100,000 |
| Certified exit and right-sized support | US$2,850,000 |
| Shelfware removed from support | 214 licenses |
| The client keeps | US$4,250,000 |
The full case is in our client case studies.
The question we see most often is what to do when Java is wrapped into an expiring ULA. The answer sits in your ordering document: you may deploy only what the contract names. If Java SE is an ordered program, count it in the same discovery as everything else and certify it on the same basis, checking any restrictions on certification that apply to it.
If Java SE is not named, it sits outside the ULA, and the Java SE Universal Subscription applies instead. That subscription has been priced per employee since January 2023. Oracle products that include Java are licensed to use that Java for that product only.
How do we certify our Oracle ULA when Java is bundled in?
Should we include Java when negotiating or exiting an Oracle ULA?
Our ULA is expiring and Java is wrapped into it: certify, renew or migrate?
ULA licenses may be used on the authorized clouds, but deployments there usually cannot be counted when you certify. Many older ULAs are silent or restrictive on public cloud, and Oracle will exclude those deployments at certification; some ULAs include cloud rights, and the wording matters.
Every database moved before certificationis one you will not own licenses for afterwards, unless the contract counts it.
Plan the migration and the exit togetherDecide what moves, and when, against what the certification will count.
Read the contract firstWe review the cloud wording before any cloud deployment goes into the declaration.
How Oracle counts licenses on each cloud: licensing Oracle in the cloud.
Ordering documentsStandard and non-standard language.
Product policiesStandard licensing policies for each product, option, pack and module.
Usage rightsSpecial usage rights, if any.
RestrictionsOn deployment and usage, and on certification.
SupportSupport costs and contract terms.
Unwritten obligationsNon-contractual but traditionally accepted obligations, and your deployment status.
The futureFuture obligations and terms.
The cost of an expert is minuscule compared with the value of the savings. We have seen Oracle charge very high renewal fees to customers who wanted to certify but made mistakes.
Oracle licensing expertsSheshagiri Anegondi, our Managing Partner and a former Oracle Vice President, personally assists customers who certify or renew.
IndependentNo conflict of interest: we take no fees, commissions or partnerships from any vendor.
A guaranteed processIf you follow our recommendations, we guarantee the certification process, and any challenge to the certified position within three years is ours to answer.
End to endDiscovery, contract review, planning, the Oracle Server Worksheet, Oracle’s questions and the closing engagement with Oracle.
An Unlimited License Agreement is a contract that lets you deploy unlimited quantities of specified Oracle products for a fixed term, usually three to five years, for an upfront fee plus annual support. At the end of the term, you either certify the deployments into perpetual licenses or renew the ULA, often at a higher cost.
We advise that the first option should be to certify. Renewal makes sense only if you genuinely need substantial new Oracle deployment over the next 3 to 5 years. Most customers we work with find that certification gives them more than enough perpetual licenses for their real needs, at a fraction of the renewal cost. The decision should be data-led, not fear-led.
Twelve to eighteen months before expiry, at the latest; earlier is better. Certification needs deployment discovery, deployment ramp-up where appropriate, contract review and a carefully managed engagement with Oracle. Customers who start three months out almost always end up renewing because they ran out of time.
Renewal earns Oracle more than certification. Oracle’s sales team is incentivized to renew, expand product scope and lift price, and its playbook is to seed doubt about your deployment count, virtualization compliance and future growth, so renewal feels safer.
Failure usually means a forced renewal at higher cost, with expanded product scope and new compliance traps. Some customers also face audit findings for products outside the ULA. The cost routinely runs into millions.
If Java SE is an ordered program, include it in the enterprise-wide count and check any restrictions on certification that apply to it. If it is not, it is outside the ULA and needs its own licensing. The ordering document settles which case you are in.
That depends on what the ordering document says about Java, and we do not answer it without reading the contract. Do not volunteer information the contract does not require.
The OSW is the Excel-based declaration Oracle uses to record your certified deployments. How you fill it in sets your perpetual license count for the next decade. Common mistakes, such as under-counting environments, mis-mapping virtualization or forgetting DR, directly reduce your future entitlement.
It depends on the ULA contract. Many older ULAs are silent or restrictive on public cloud, and Oracle will exclude those deployments at certification. Some ULAs include cloud rights, but the wording matters, so we review the contract before any cloud deployment goes into the declaration.
Sometimes, but it needs careful contract interpretation and timing. Oracle’s standard M&A grace period gives some room to absorb acquisitions up to a certain size, but the certification rules are stricter. We have certified ULAs covering acquisitions, divestitures and joint ventures; the planning has to start well before the corporate event closes.
Your support stream typically stays at the level set during the ULA; Oracle’s matching-support rule generally prevents you reducing it just because your perpetual license count is now defined. After certification is the right time to look at support cost reduction across the whole Oracle estate.
Yes: deployment discovery, contract review, pre-certification planning, the OSW, Oracle’s clarification questions and the closing engagement with Oracle. Your team takes part where its input is needed, but we own the process and the outcome alongside you.
No. Rythium is independent and does not resell licenses or support, or earn income from Oracle or any support provider.
Tell us when your ULA ends and what it covers. We will show you what certification would give you, and what Oracle will try to change.
Cookies on rythium.com
We use essential cookies to make this site work, and additional cookies to measure visits and our ads. You can reject the additional ones or choose which to keep. Privacy Policy