Oracle Licensing Guide: ULAs, Java, Audits and Support

Independent guide to Oracle licensing: ULA certification and renewal, Java employee-based licensing, audits, support costs, and Oracle Cloud contracts.

Many of the biggest Oracle licensing costs are decided at a few points: when an Unlimited License Agreement ends, when support comes up for renewal, when Oracle gets in touch about Java, or when an audit notice lands. Decisions made at those points are hard to undo. A certified ULA count becomes your perpetual entitlement, and support fees carry forward into every year that follows.

This guide brings our Oracle articles together by topic. Each section summarizes what you need to know and links to the full articles underneath. ULAs come first because they make up most of our Oracle writing, followed by Java, audits, and support and cloud contracts.

How Oracle’s commercial model has shifted

Formal Oracle audit activity has dropped sharply in recent years. Audit teams have been reduced and Oracle’s attention has moved toward OCI and AI. Audits still happen, but the commercial pressure now sits mostly in long-term contracts: support agreements, bundled entitlements and subscriptions that renew automatically.

Support is where most of the long-term cost builds up. Standard support is 22% of the net license fee and rises over time. Dropping licenses you no longer use is harder than it sounds, because Oracle may reprice the licenses you keep at full list price and remove the volume discounts you had before.

ULAs fit the same pattern. They bring future license spend forward into a single deal, and they lock in a support stream that is hard to reduce later, which is part of why Oracle sales teams promote them.

Read more:

1. How Oracle ULAs work

An Oracle Unlimited License Agreement lets you deploy a defined set of Oracle products without limit for a fixed term, usually three to five years, in return for an upfront fee plus annual support. At the end of the term you either certify, which converts your deployments into perpetual licenses, or renew for another term.

There are variations. A Perpetual ULA (PULA) has no certification and allows unlimited use indefinitely, at a higher cost. A Term ULA runs for one to two years and doesn’t convert into perpetual licenses at all.

“Unlimited” only applies within the contract’s scope, and ULAs vary, so the wording of your own agreement is what counts. Only the legal entities and products listed in the contract are covered. If you’ve licensed Database Enterprise Edition, for example, Standard Edition 2 isn’t included unless it’s named. Acquisitions above 10% of the organization by revenue or headcount may trigger extra licensing or a renegotiation.

Virtualization and cloud need particular care. Oracle doesn’t accept soft partitioning, such as VMware, as a way of limiting license counts. Hard partitioning, such as Oracle VM or IBM LPAR, is accepted if it’s properly implemented and evidenced. Oracle also distinguishes authorized clouds (OCI, AWS, Azure and GCP) from non-authorized ones. Deployments in a non-authorized cloud may not count toward certification, and some ULAs prohibit cloud use after certification altogether.

Read more:

2. What a ULA really costs

The upfront fee is priced on the growth Oracle expects you to have during the term. Annual support is typically around 22% of the contract value. It’s calculated on that value rather than on what you deploy, so it doesn’t fall if usage drops, and it continues after certification.

A ULA works out cheaper than traditional licensing when usage grows quickly and deployments are tracked well. When growth slows, traditional licensing is usually more economical. Before you sign or renew, benchmark the ULA against what the same estate would cost on standard licenses, and model support across the whole term.

In practice, the realistic opportunity to bring support costs down comes after certification, through negotiation and repricing.

Read more:

3. Managing a ULA during the term

Most ULAs that go wrong do so after signing. A ULA fixes your license spend for the term, but cost efficiency, audit protection and a clean certification all depend on how it’s managed.

Track deployments continuously in your own asset management system rather than relying on Oracle’s tools, and run internal audits at set intervals. Oracle audits often take place close to the end of a ULA term or soon after it, and weak records at that point can turn certification into a compliance dispute.

The mistakes we see most often are assuming every Oracle product is covered, keeping thin deployment records in virtualized and cloud environments, overestimating growth, and leaving certification planning too late. Start modeling exit, renewal and transition options well before the final year, because waiting for Oracle to raise them reduces your room to negotiate.

Cancelling a ULA mid-term is rare. It can bring termination fees, the loss of unlimited deployment rights and closer audit scrutiny, so take independent advice before raising it with Oracle.

Read more:

4. The end of a ULA: certify or renew

As a ULA approaches expiry there are two meaningful paths. Certification converts your deployments into a fixed set of perpetual licenses and ends unlimited deployment rights. Renewal extends those rights into a new term, typically three years, under revised commercial terms.

Oracle usually prefers renewal. An active ULA keeps support growing and preserves future licensing opportunities, while certification caps expansion revenue. That’s why certification is often presented as complex or risky.

The decision should rest on your actual deployment trends, platform strategy, and plans for cloud and virtualization. Certifying when growth has stabilized can remove unnecessary cost. Renewing while growth is still accelerating can make commercial sense, as long as the terms are tightly controlled. Where organizations lose ground is in entering renewal talks without validated usage data, letting Oracle set the timeline, or treating support baselines as fixed when they can be negotiated.

PULAs raise a similar question at renewal. In July 2026 we published a case study on a North American organization with turnover above $20 billion and more than 20,000 employees. After years of unrestricted deployment, staff turnover, acquisitions and divestments, it had no reliable view of its Oracle usage. We ran a structured data collection program, cross-checked the results against its self-declared outputs, and evaluated the renewal and exit scenarios against its future plans.

Read more:

5. Certifying a ULA

Once Oracle accepts your certification, the quantities become your perpetual entitlement baseline. Under-certify and your entitlement is fixed below what you actually run, so any growth beyond it needs new licenses.

Certification draws on infrastructure, procurement, legal and finance, and it starts with the contract: covered products, entities, territory, deployment definitions and virtualization clauses. Discovery then has to find every installation across physical servers, virtual clusters, data centers and public cloud, before the technical data is translated into licensing metrics using Oracle’s processor core factors.

Start at least 12 months before expiry, and ideally 18. Cloud environments often need 12 months of historical daily average data, and that can’t be recreated after the fact. Virtualized estates need early attention too, because Oracle’s position on soft partitioning can change licensable quantities significantly. Contract wording also matters: “installed AND running” and “installed and/or running” can produce different counts.

Don’t rely only on Oracle-supplied scripts, and test your own assumptions independently before you submit. In a case study published in June 2025, Virellio Technologies had a virtual environment of more than 100,000 processor cores. We started well before its certification deadline, measured ULA and non-ULA usage several times, and found database configuration issues that could have inflated Oracle’s claims. Virellio avoided more than $500 million in potential license exposure and agreed a defined licensing model for its full virtual estate.

Read more:

6. After certification: exit, renew or renegotiate

Certification ends the agreement, but Oracle often uses it to reopen commercial discussions. Renewal conversations frequently begin before certification is complete.

You can exit and keep paying support on your perpetual licenses, which suits organizations whose growth has leveled off. You can renew, which can make sense when major expansion or cloud migration is planned. Or you can renegotiate into a different structure, such as a hybrid agreement, capacity-based licensing, an Oracle cloud or subscription agreement, or license purchases matched to real usage.

Certification also gives you something useful for that negotiation: a verified view of your deployed footprint, your usage patterns and your support baseline. Analyze your long-term requirements before renewal talks begin, and avoid committing to renewal terms while certification is still underway.

Our ULA strategy guide pulls the full lifecycle together, from signing through certification and beyond.

Read more:

7. Oracle Java: when does licensing apply?

For years Java was treated as free background infrastructure. That changed when Oracle moved to the Java SE Universal Subscription in 2023, which licenses Java by employee count rather than by installation, processor or user.

The employee definition is broad. It can include full-time and part-time staff, temporary workers, and contractors who support internal operations. Cost therefore follows the size of your organization, regardless of how many systems run Java. Take an organization with 10,000 employees and Oracle Java on 2,000 PCs. Licensing would typically be calculated on all 10,000, and at Oracle’s published pricing tiers that could approach $990,000 a year.

Finding Java in your estate doesn’t automatically mean you owe Oracle anything. Start by working out what you’re running: Oracle JDK, OpenJDK, a vendor’s OpenJDK build, or Oracle Java used under specific no-cost terms such as the OTN license or Oracle’s No-Fee Terms and Conditions (NFTC). Those no-cost rights don’t cover every release or every kind of use, so downloading Oracle Java for free doesn’t make every later use free.

Java bundled inside a third-party application needs checking too. Java in ERP, HR, payroll and BI systems may be covered under Oracle’s redistribution terms, but only when it’s used exclusively within that package. Your contract with the software vendor should state your right to use Oracle Java. Without that, you may need your own subscription.

Read more:

8. How Oracle sees your Java usage

Oracle doesn’t need an audit to find Java. Java connects to Oracle automatically when it checks for updates and security patches, so Oracle already has a view of where it’s installed. Downloads can be tied to an organization’s IP address, and update checks are logged with details such as network domain, version and timing. Organizations using Oracle’s Java Management Service send usage data to Oracle directly.

With that visibility in place, Oracle needs only your headcount to issue a recurring invoice, and a single unlicensed installation can trigger the obligation for the whole organization.

This changes how you defend against a Java claim. With database or middleware audits, there’s usually a chance to pause, review internally and fix gaps before any data is shared. With Java the discovery has effectively already happened, so the only real protection is establishing your position before Oracle gets in touch.

That’s the approach we took with Tarynx, an energy company with more than 2,000 employees, in a case study published in May 2025. Commercial Java was part of its standard machine build. Our discovery produced over a million data points, and more than 90% of the installations turned out to pose no licensing issue. Tarynx avoided a potential claim of up to $1.44 million, based on a five-year Java subscription.

Read more:

9. Reducing your Java exposure

A Java strategy starts with knowing where Java is deployed, which distributions and versions you run, and which applications depend on it. From there you can restrict Oracle Java to the systems that genuinely need it, disable automatic updates where it’s practical, and make sure IT and procurement teams understand the licensing rules. Stopping Oracle Java use doesn’t necessarily clear past exposure, so this is worth doing before Oracle raises the subject.

Many organizations have moved some or all of their estate to other distributions. OpenJDK, Azul Zulu, Eclipse Temurin, Amazon Corretto, IBM Semeru and BellSoft Liberica are all established options, and several offer free versions alongside paid support. GraalVM is aimed at specialized, performance-focused use and isn’t a direct replacement for a standard runtime.

If you migrate, assess compatibility first, settle on one or two approved distributions, and move in phases, starting with non-critical systems. Make sure Oracle Java is fully removed or properly isolated at the end. A partial migration can leave you with the same exposure you set out to remove.

Read more:

10. Oracle audits

For database, middleware and other technology audits, there’s a sequence that protects you. Pause the audit, carry out a structured internal review, stabilize your license position and close any configuration gaps before data goes to Oracle. If Oracle’s findings don’t match the verified facts, challenge them with evidence and your contract terms.

East Coast Health Partners, a healthcare provider with nearly 30 practice locations, faced $1 million of technology licensing risk and another $1 million on E-Business Suite after an Oracle audit notice. In our case study from April 2025, we postponed the audit by four months so its IT team could close the gaps first, and advised on keeping irrelevant hardware and virtualized VMware environments out of what was disclosed. The technology claim ended in a negotiated payment of $130,000, and nothing was owed on E-Business Suite.

Audits often follow commercial changes. An industrial machinery supplier expected one after cancelling Oracle Database and Middleware support and moving to Rimini Street. Our March 2025 case study describes how we found and closed a significant compliance gap, and removed its need for an Oracle Java subscription covering all employees. The Oracle audit that followed within six months ended with no claims.

Divestitures carry their own risk, because licenses that move between companies often arrive with poor documentation. Dynarion, a technology provider with about 4,000 employees, had acquired E-Business Suite licenses that way and faced a worst-case exposure of €20 million as its price hold ran out. Our January 2025 case study covers the internal audit and contract review that established its actual position, and Dynarion avoided buying licenses it didn’t need.

Read more:

11. Support costs, cloud and Fusion contracts

Oracle support fees have risen sharply, and contract terms such as License Set and Matching Service Levels make them difficult to reduce. Cutting products or license counts can lead Oracle to lower the discounts on what remains, which can cancel out the saving. Many organizations end up paying support on licenses they no longer use.

Reductions are still possible with a detailed review of licenses, contracts and actual usage, followed by a negotiation strategy that avoids compliance and operational risk. A Dutch medical center had spent two years trying to bring its Oracle support costs down while its use of Oracle products declined. In our March 2024 case study, we built an Effective License Position, identified surplus licenses and took over negotiations with Oracle. The yearly saving was equal to more than four nurses’ salaries.

Oracle Cloud contracts are layered: a master agreement such as the Cloud Services Agreement, ordering documents with services, quantities and pricing, and service descriptions. Older purchases may still sit under legacy models such as Universal Cloud Network. Automatic renewals often leave little time to check usage, and entitlements can overlap. One client found during a pre-renewal health check that it was paying for OCI Compute under two contracts, one at promotional pricing and one at full rate. Treat each renewal as a fresh purchase you can renegotiate.

Fusion licensing has its own metrics. Hosted Named User counts every authorized user, whether or not they use the service, so former employees with live accounts still cost you licenses. Hosted Employee covers all employees, including contractors and consultants. The “Each” metric wasn’t defined in Oracle’s June 2024 price list. Oracle is also encouraging on-premises E-Business Suite customers to move to Fusion Cloud ERP, which is likely to be much harder to reverse than a database migration.

Read more:

Oracle case studies

Oracle PULA Assessment Guides Strategic Renewal Decision (July 2026): An independent assessment of a North American organization’s Oracle estate ahead of its PULA renewal, covering renewal and exit scenarios.
ITAA Secures $500M Risk Avoidance in ULA Exit (June 2025): Virellio Technologies certified its ULA across more than 100,000 virtual cores and avoided over $500 million in potential exposure.
Leading Energy Firm Averts $1.44M Oracle Java Claim (May 2025): Java discovery across Tarynx’s estate showed more than 90% of installations posed no licensing issue.
Healthcare Avoids $1.87M Oracle Risk via ITAA Audit Defense (April 2025): A four-month audit postponement and remediation brought East Coast Health Partners’ technology claim down to $130,000.
Oracle Compliance and Cost Savings for an Industrial Leader (March 2025): An industrial supplier closed its compliance gap before moving to third-party support, then passed an Oracle audit with no claims.
Navigating Oracle Licensing Risks Post Divestiture (January 2025): Dynarion clarified E-Business Suite licenses acquired through a divestiture and avoided a worst-case €20 million exposure.
Annual Support Saving Equal to Four Nurses’ Salaries (March 2024): A Dutch medical center cut its Oracle support costs after two years of unsuccessful attempts on its own.
Oracle License Compliance: €3m Settlement Costs Saved (May 2021): Technical analysis after an Oracle audit brought Violis’s position down from a €3.5 million impasse to around €300,000.

10. FAQ

Do we need an Oracle license if Java is installed?

Not necessarily. It depends on the distribution, the version, how it’s used and which licensing terms apply. OpenJDK builds and some Oracle releases used under no-cost terms may not need a paid subscription, but that needs checking release by release.

Should we certify or renew our Oracle ULA?

It depends on your growth. Certification often makes sense when deployments have stabilized, and renewal may be worth considering if significant expansion is planned. Either way, the decision is stronger when it’s based on validated usage data rather than on the timeline Oracle sets.

When should we start preparing for ULA

Usually 12 to 18 months before expiry. Cloud environments can need 12 months of historical daily average data, which is difficult to rebuild later.

Can Oracle support costs be reduced?

Often, but it takes care. Dropping licenses can lead Oracle to reprice the ones you keep, so reductions need a detailed review of contracts and usage and a planned negotiation. For ULAs, the main opportunity usually comes after certification.

Does Oracle still audit its customers?

Yes, though formal audit activity has fallen in recent years. Audits can still follow commercial events such as the end of a ULA term or cancelling support, and Java is handled differently because Oracle already has visibility of installations through update checks.

Talk to our Oracle team

Whether you’re approaching the end of a ULA, reviewing Java, or preparing for a support renewal, our Oracle specialists can help you understand your position before Oracle sets the agenda. Explore our Oracle services or get in touch.