Oracle ULA Certification: What You Keep and How to Certify

The short answer: Oracle ULA certification is the formal step at the end of an Oracle Unlimited License Agreement. You count every deployment of the products named in the contract and declare that count to Oracle. Once Oracle verifies it, the declared quantity becomes your perpetual licence quantity, subject to the terms of the agreement. The alternative is renewal, which means a new term and a new fee, and Oracle would usually rather you renewed.

In short

• Certification is also called exit. You count, declare and keep what is deployed as perpetual licences.
• Your licences do not expire when the term ends, and the ULA gives you the right to certify. Renewal is not a requirement.
• Whatever you can legitimately count on certification day, you keep. Whatever you miss, you buy again later.
• Only products named in your contract, and deployments the contract allows, can be certified. Every ULA is different, so the contract review comes first.
• Start 12 to 18 months before the end date at the latest. Less time puts the decision in Oracle’s hands.
• If Java is wrapped into your ULA, check the ordering document first.

Sheshagiri Anegondi

The Best Oracle ULA Is One You Never Renew

A ULA can be certified: you declare what you have deployed and keep those licenses for good, instead of paying more at every renewal.

Short · 0:54Watch on YouTube

What certification is and what you keep

A ULA is not unlimited in every direction. It gives you an unlimited deployment right for a specific set of Oracle programs, for a limited number of legal entities, and for a limited period. The term is usually three to five years, as our guide to what an Oracle ULA is explains.

At the end of the term, the ULA gives you a perpetual grant of licences for what you have deployed. Certification is how you claim it. A C-level executive of your company signs the certified count, and Oracle then verifies the numbers, either by discussion or through a formal audit. After verification, Oracle grants the perpetual licences. The certification date is generally 30 days after the end of the term, but your contract sets the exact date, so read it.

Anything you deploy beyond the certified count needs new licences, and what you miss on certification day you do not keep.

Certify or renew

Many customers believe they have to renew. They do not. As our Managing Partner Sheshagiri Anegondi writes, “the ULA does not even talk about renewal.” The contract gives you the right to certify.

Our advice is to treat certification as the first option. Renewal makes sense only when growth is ahead of you, and the decision should be led by data, not by fear.

Oracle earns substantial revenue from ULAs. A renewal brings a new annual support fee linked to the licence cost, and a certification does not. A certified customer also owns perpetual licences and is free to move away from Oracle later. So Oracle often makes certification slow and full of obstacles.

The worst outcome is a forced renewal. It happens when you have deployed outside the terms of the ULA and a renewal looks safer than the potential shortfall bill. Fix gaps during the term, not at the end. If you are weighing other agreement types, see ULA or PULA.

The certification process step by step

Our full sequence is the 12 step Oracle ULA certification or renewal process. At its core are five stages, which we call the five C’s, set out in detail in the Oracle ULA certification checklist. The order matters. Skip one or run them out of sequence and you either leave perpetual rights on the table or walk into a compliance gap.

1. Contract review. Read the ordering documents, the master agreement and every amendment. Check the standard and non-standard language, the licensing policy for each product, special usage rights, restrictions on deployment and on certification, and support costs.
2. Count. Run a discovery across the whole enterprise and every data centre, covering known and unknown Oracle deployments. Include virtualised and cloud environments, even those set up outside central IT.
3. Comply. Remediate usage that exceeds what the contract allows, and rebalance the estate by consolidating and decommissioning unused software.
4. Count again. Remediation changes the estate, so run a second discovery. Certifying against a stale count is how clean positions turn into disputes.
5. Certify. Submit the declaration, with documentation you can defend. Oracle may verify it through an audit, review the paperwork and speak to your team.

Oracle’s process uses the Oracle Server Worksheet, a spreadsheet of your servers, data centres, virtualisation and Oracle installations. Under-counting environments and forgetting disaster recovery reduce what you are granted. Sheshagiri adds that the agreement does not ask for script outputs at certification. It asks for a correct declaration, built on a detailed internal compliance review, and Oracle keeps the right to audit if it sees a discrepancy.

What counts and what does not

The licences you can certify are decided by the terms of your contract, not by a sales rep’s phrase that “everything deployed counts”. As Sheshagiri puts it, no two ULA contracts are exactly the same. A few rules hold in every case.

• Named products only. You may deploy only the products listed in the contract. Even features slightly connected to them are not covered. Use outside the list has led to audits during the term and to very large licence fees.
• Virtualised estates. Oracle’s partitioning policy says VMware and other soft partitioning are not permitted as a means to limit the number of licences. The policy also says it may not be incorporated into any contract, so the wording of your agreement matters.
• Public cloud. Whether deployments on AWS, Azure or Google Cloud are included depends on your ULA contract. Many older ULAs are silent or restrictive on cloud, and Oracle will exclude those deployments. Our guide to licensing Oracle on cloud covers Oracle’s counting rules.
• Mergers and acquisitions. Oracle does not carry a ULA over if your company is merged or acquired. This can be managed, but only if you act in time.

Java and the ULA

The question we see most often is what to do when Java is wrapped into an expiring ULA. The answer sits in your contract.

Start with the ordering document. The rule is the same as for every other product: you may deploy only what the contract names. Check whether Java SE appears among the ordered programs, and read the licence definitions and rules and any restrictions on certification that apply to it. Oracle’s Java SE FAQ (updated 20 October 2026) adds that Oracle products which include Java are licensed to use that Java for that product only.

If Java SE is in the ULA, count it in the same discovery as everything else and certify it on the same basis. If it is not, it sits outside the ULA, and the Java SE Universal Subscription applies instead. That subscription has been priced per employee since January 2023, and the count includes part-time and temporary staff and contractors who support internal operations.

The migrate option needs the Java version in front of you. Oracle JDK 25 is free under the Oracle No-Fee Terms and Conditions until September 2028. Later updates of JDK 21 (after 21.0.12), JDK 17 (after 17.0.13), JDK 11 and JDK 8 (from 8u211) fall under the Oracle Technology Network licence, which needs a subscription for production use. Our Java license review maps which of those you run. Whether Java belongs in a ULA negotiation or exit is part of what we review.

Timelines

Certification is not a paperwork exercise. We recommend starting 12 to 18 months before the end date at the latest, and earlier is better.

Oracle’s deadline is its main lever. Begin early enough that certify or renew stays your decision. Remediation and a clean re-count only work while the unlimited window is open. Everything you deploy inside the term, within what the contract allows, counts toward the perpetual grant at no further cost. The same deployment after certification is a purchase. Document as you go, since evidence is easier to assemble in real time than to rebuild once Oracle asks.

Mistakes that cost money

Sheshagiri lists ten of them in the 10 things customers get wrong about the Oracle ULA. These hurt most at certification.

• Assuming the ULA protects you from audit. It does not. Oracle keeps the right to audit during the term, and Sheshagiri notes that almost 60% of ULA customers are either audited during the term or forced to buy additional products to avoid the audit.
• Disclosing more than the contract requires. In Sheshagiri’s words, “confidentiality is key to both a successful certification and a low-priced ULA renewal.”
• Treating certification as a form to file at the end. A bank we describe in the cost of failing an Oracle ULA certification asked Oracle for the process one month before the term ended. Oracle proposed to grant up to 20% of the expected licences on three products and nothing on two others, and asked for more licences on two products outside the ULA across the whole virtualised estate. The bank renewed for US $4.5 million over three years, with no additional Oracle usage needed.

After certification

Support does not fall away when you certify. Sheshagiri is clear that the support costs fixed at the start of the ULA stay the same after you exit, and that the number of licences you declare does not change them. Oracle prices support at 22% of the net licence fee a year, and ending support on part of an order reprices what remains, so changes need care. Removing licences nobody uses from support can still lower the bill, as the bank below did, if it is planned around those repricing rules. Our page on Oracle third-party support sets out the alternatives.

Expect Oracle to look at your declaration. It may review the documents, request evidence and interview your team, so the counting has to hold up. If you miss a deployment, you lose the perpetual right to it, and getting it back means buying it.

How Rythium helps

We are an independent advisory. We have no partnership with any software publisher and we do not sell licences. We have run more than 260 engagements since 2015, and we have helped more than 150 customers certify an Oracle ULA.

One recent engagement shows the effect of starting early. The client is a bank, and its name is withheld.

For the service itself, see our Oracle ULA exit process page, or contact us to talk about your end date.

Questions we are asked about Oracle ULA certification

Our Oracle ULA is expiring and Java is wrapped into it. Should we certify, renew, or migrate?

Decide on the same basis as the rest of the ULA: renew only if you need substantial new Oracle deployment over the next three to five years. First check whether Java SE is named in the ordering document, because you can deploy only what the contract lists. We review this as part of the contract review.

How do we certify our Oracle ULA when Java is bundled in?

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.

Should we include Java when negotiating or exiting an Oracle ULA?

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.

Can we certify an Oracle ULA with deployments on AWS?

It depends on the ULA contract. Many older ULAs are silent or restrictive on public cloud, and Oracle will exclude those deployments at certification. We review the contract before any cloud deployments go into the declaration.

How do we avoid a forced Oracle ULA renewal?

Run a detailed compliance review months before the term ends, fix gaps while the unlimited window is open, and compare certification against renewal on cost.