Oracle License Cost Optimization in 2026: Five Trends and What to Do About Them

Oracle’s sales strategy has a pattern, and it is predictable enough to plan around. Every year the same five pressures land on Oracle customers: Unlimited License Agreements pushed towards renewal, cloud commitments folded into contracts, Exadata offered as a service, Java billed on a new metric, and audits used as a sales tool. None of them is new in 2026. What has changed is how far each has gone, and how much it costs a customer who meets it unprepared.

These are the five trends we expect to shape Oracle spending through 2026, and what we recommend doing about each.

In short

• ULAs: Oracle pushes renewal. Certification is a one-time count you make within 30 days of the end of the term; decide between the two at least a year ahead, after measuring what you have deployed.
• Cloud in the contract: Oracle Cloud Infrastructure credits are bundled into renewals and rewarded through Oracle Support Rewards. Commit only to credits you are sure to consume.
• Exadata as a service: Cloud@Customer and Oracle Database@AWS, @Azure and @Google Cloud are sold as cloud. Compare licence-included and bring-your-own-licence prices on your own workload.
• Java: Oracle’s Java subscription is priced per employee, and free updates for JDK 21 ended in September 2026. Inventory Java now and move what you can to free OpenJDK builds.
• Audits: Oracle’s licensing team is part of the sales process. Route every Oracle request through one owner and take independent advice before you share data or run scripts.

1. ULA renewals, pushed early and hard

An Unlimited License Agreement lets you deploy named Oracle products without limit for a fixed term, usually three to five years. At the end you either renew or certify: you count everything deployed and keep it as perpetual licences. The certification has to be made within 30 days of the end of the term, so the count, and any clean-up behind it, must be finished before then.

Oracle prefers renewal, because certification ends the relationship’s leverage. Expect renewal proposals a year or more before the end date, often with an audit question or a compliance concern attached, and often with cloud credits added to the price.

What to do: Measure your deployments at least 12 months before the end of the term, fix anything outside the ULA’s scope, and decide between renewal and certification on your own numbers. If you certify, deployments on AWS, Azure and Google Cloud cannot be counted, so plan migrations around the certification date. Our ULA certification work starts with that timeline.

2. Oracle Cloud folded into the contract

Oracle Cloud Infrastructure is now part of most large Oracle negotiations. Renewals arrive with Universal Credits included, and Oracle Support Rewards credits a share of your Oracle Cloud spending against the support bill for your on-premises licences: 25 cents per dollar spent, 33 cents for ULA customers.

The offers can be good value when the workloads are real. The risk is commitment without consumption: annual credits that are not used expire, and a renewal priced around cloud spend you never make leaves you paying for both.

What to do: Price any cloud commitment against a migration plan with dates, keep cloud credits separate from licence and support terms in the paper, and compare Oracle Cloud with AWS, Azure and Google Cloud on licence counts as well as compute. On Oracle Cloud one processor licence covers two OCPUs (two cores); on the other three clouds it covers two vCPUs (one core), which often decides the comparison. Our guide to licensing Oracle in the cloud sets out each rule.

3. Exadata sold as a service

Exadata Cloud@Customer puts Oracle’s Exadata hardware in your data centre on a subscription. Oracle Database@AWS, @Azure and @Google Cloud put the same Exadata and Autonomous Database services inside the hyperscalers’ data centres. Both are licensed on Oracle Cloud’s terms, either licence-included or with licences you bring, and both come with multi-year commitments.

What to do: Compare licence-included against bring-your-own-licence on your own database sizes and options, check the minimum term and what happens to your licences and support if you leave, and do not let the subscription replace licences you already own and support without a credit for them.

4. Java on a per-employee subscription

Since January 2023, Oracle has sold new Java SE subscriptions only as the Java SE Universal Subscription, priced on the number of employees in the whole organisation, not on the computers that run Java. List prices start at $15 per employee per month. A company with 5,000 employees and a few hundred Java installations pays for all 5,000.

The free routes keep narrowing. Oracle JDK 17 and 21 were released under a no-fee licence, but only until a year after the next long-term release: free updates for JDK 17 ended in September 2024, and for JDK 21 in September 2026. Later updates come under Oracle’s OTN licence, which does not allow commercial production use without a subscription. Oracle’s Java sales team contacts companies whose downloads it can see, and those letters are the start of a compliance process.

What to do: Find every Oracle Java installation, including those bundled inside other products, which are often licensed through the product. Move what you can to free OpenJDK builds such as Eclipse Temurin, Amazon Corretto or Azul Zulu, and keep a record of what remains. Our Java defense work is priced on that footprint, not on your payroll.

5. Audits as part of the sale

Oracle’s audit team, now called Global Licensing and Advisory Services (formerly License Management Services), works alongside sales. Audits and softer “licence reviews” tend to arrive near the end of Oracle’s financial quarters, before renewals, and when a customer declines a cloud or ULA offer. A finding is then settled by buying something, often the offer that was declined.

What to do: Treat any request for deployment data as the start of an audit, whatever it is called. Name one person to handle all Oracle licensing contact, read your contract’s audit clause (most give Oracle 45 days’ notice and limit the audit to your use of the programs), and take independent advice before sharing data or running Oracle’s scripts. Our Oracle audit defense page explains how we manage the process.

What to do this year

• Run your own count of Oracle deployments, options and Java installations, before Oracle asks for one.
• Put every Oracle contract end date, ULA term and support renewal on one calendar, with a decision date a year before each.
• Price any cloud or Exadata subscription against what you already own and support.
• Reduce the estate before you negotiate: unused options, packs and Java installations are the easiest savings.
• Keep the conversation with Oracle in one place, and in writing.

Questions we are asked about Oracle license optimization

How can I reduce Oracle licensing costs?

Start with what you use: switch off unlicensed options and packs, consolidate databases onto fewer licensed servers, move suitable workloads to Standard Edition 2, contain Oracle in dedicated virtual clusters and move Java to free OpenJDK builds. Then negotiate renewals and cloud commitments on your own numbers.

Should I renew or certify my Oracle ULA?

Certify if your deployments are stable and you can count them cleanly; renew only if you expect strong growth in the products the ULA covers. Measure first, at least 12 months before the end of the term.

Is Oracle Java still free?

Only in limited cases. Oracle JDK 25 is free under Oracle’s no-fee licence until a year after the next long-term release; earlier versions now need a subscription for commercial use. OpenJDK builds such as Temurin and Corretto are free.

What is Oracle GLAS?

Global Licensing and Advisory Services, Oracle’s licensing and audit team, formerly called License Management Services (LMS).

What is Oracle Support Rewards?

A programme that credits part of your Oracle Cloud Infrastructure spending against your on-premises support bill: 25 cents per dollar, or 33 cents for ULA customers.

The best time to optimise Oracle spending is a year before a renewal, not a week before. Book an hour with our Advisor on Call to look at your next Oracle decision, or talk to us about a full review.