Oracle ULA: 10 Things Customers Get Wrong and How to Get Them Right

Most of what customers believe about the Oracle Unlimited License Agreement (ULA) comes from conversations with Oracle’s own sales teams. Some of those beliefs cost customers a great deal at certification and renewal time. Here are the ten I hear most often, what the contract actually says, and five moves that put the customer back in control.

10 things customers get wrong about the Oracle ULA

1. Do your Oracle licenses expire when the ULA term ends?

No. In fact, the opposite is true. Oracle ULAs specifically provide a perpetual grant of licenses at the end of the term.

2. Do you have to renew an Oracle ULA?

No. The ULA specifies that the customer has the right to certify the ULA. In fact, the ULA does not even talk about renewal.

3. Will certifying a larger number of licenses increase your support costs?

Not at all. The support costs that were fixed at the start of the ULA will continue to remain the same after you exit (that is, certify the ULA). The number of licenses that you declare for certification will not change the support costs.

4. Is your company safe from an Oracle audit during the ULA term?

No. Oracle maintains the right to audit even during the term of the ULA. In fact, almost 60% of ULA customers are either audited during the term of the ULA or forced to purchase additional products to avoid the audit.

5. Can every license deployed during the ULA be certified?

Not really. While Oracle sales reps are known to use this phrase, the truth is that the licenses that can be certified are determined by the terms in the contract. And every ULA contract is different. No two ULA contracts are exactly the same.

6. Does an Oracle ULA allow you to deploy all Oracle products?

Absolutely not. The customer has the right to deploy only those products that are specifically mentioned in the contract. Even features slightly connected to these products are not allowed to be used during the contract. This mistaken understanding has led to multiple audits during the ULA term and to very large license fees paid to Oracle.

7. Do you have to “true up” at the end of the ULA term?

No. In fact, the opposite is true. The Oracle ULA allows you to get a perpetual license grant of all the licenses that you have deployed (subject to the terms in the agreement).

8. Do you have to run Oracle’s scripts before you give Oracle the certification declaration?

No. The agreement does not ask for script outputs to be provided to Oracle at the time of certification. (But, yes, Oracle maintains the right to audit if they feel there is a discrepancy in the declaration.) Customers should therefore declare the numbers correctly after conducting a very detailed internal compliance review. Our Oracle ULA certification checklist lists what that review covers.

9. Will Oracle carry the ULA over if your company is merged or acquired?

No. This is one of the major risks of a ULA, and it can lead to the loss of the huge investments that companies have made in their Oracle deployments over 3 to 20 years. There are ways to overcome this if action is taken in time; see Oracle licensing during mergers and acquisitions.

10. Is an Oracle ULA renewal always costlier than the previous ULA?

This is an interesting one. Yes, if you do not control the conversation with Oracle. No, if you know what to disclose to Oracle and how to set up the terms of the negotiation. During a renewal, the price can vary from much lower than the previous ULA price to many times the previous ULA price.

How to get it right: five moves for every ULA customer

If the beliefs above are not true, what should a customer do? The answer, while not very simple, is this:

1. Customers should not be afraid of Oracle during negotiations.
2. Customers should conduct a detailed and comprehensive license compliance review of their ULA deployment months in advance of the ULA term end.
3. Customers should do an objective cost-benefit analysis of the ULA certification versus renewal options.
4. Customers should not disclose information to Oracle without specifically being asked, and only if providing that information is mandated by the contract. Confidentiality is key to both a successful certification and a low-priced ULA renewal.
5. Customers should never get into a situation where they are forced to renew the ULA.

And there is help if needed. Call Rythium.

Questions customers ask about ULA certification and renewal

Should we renew our ULA because the end date is close?

A term ULA does not automatically require renewal. Your agreement and its certification provisions determine the perpetual license position at exit. A ULA gives the customer the right to deploy specified Oracle software without quantity limits for a defined term. When that term approaches its end, the decision is not simply “renew or lose everything.” The certification provisions in the agreement determine how the qualifying deployed position is recorded for ongoing use.

That makes renewal a business and licensing decision, not a step to take automatically because the end date is approaching. The key question is whether future growth still justifies another ULA term, or whether the organization is better served by preparing to certify.

Does deploying more covered software under the ULA raise support costs at exit?

Deploying more covered software does not, by itself, mean support is re-priced upward at certification. The applicable order and support terms govern the economics. One of the commercial features of a ULA is that customers can use more of the covered products during the term without paying incremental license fees each time deployment grows. Oracle’s own GLAS guidance notes that ULA usage can increase while the support stream remains flat during the agreement.

That is why organizations should understand whether they have fully used the deployment rights they already purchased before certification. But “deploy fully” should never mean “deploy indiscriminately”: only the products, entities, territories and use conditions covered by the actual ULA count.

Will maximizing deployments in the current ULA make the next renewal costlier?

There is no universal rule that a new ULA is priced as a retroactive true-up of properly covered deployments. Renewal is a new commercial decision based on future needs, scope and negotiated terms. Enterprises sometimes under-use the final months of a ULA because they fear that a larger certified position will mechanically increase the price of the next agreement. That can leave value on the table.

The better approach is to separate two questions. What rights should we legitimately use and certify under the current ULA? And what future growth, products and contractual scope do we need after it ends? A renewal can then be judged against the future requirement, instead of treating covered deployment as a reason not to make full use of the existing agreement.

Does a ULA mean zero Oracle license compliance risk?

No. “Unlimited” applies only inside the contractual scope of the ULA. Organizations can still create compliance issues through products that are outside the ULA, corporate entities that are not covered, contractual restrictions that were overlooked, or environments that receive different licensing treatment.

Certification is therefore more than an administrative count. It is the point at which the organization should understand its deployment position, identify anything outside scope and address issues before the certification process is driven by a deadline.

After a ULA, do you have to stay on Oracle support?

Not necessarily. Third-party support can be an option for suitable perpetual license estates, but support choices must be checked against Oracle’s license-set rules, matching service levels, product requirements and the customer’s own agreements. Certification and support are related, but they are not the same decision. Once the organization understands its perpetual license position, it can evaluate what support model suits the estate.

Oracle’s current Software Technical Support Policies include rules on license sets, matching service levels, reinstatement and support repricing. Some Oracle services also have their own active-support requirements. A move to third-party support should therefore be assessed deliberately rather than treated as interchangeable with Oracle support.