Top 10 Oracle Licensing and Cost Optimization Issues

The short answer: the ten Oracle licensing issues that most often push costs up for the customers we advise are pressure against ULA certification, unlicensed database options and packs, the wrong WebLogic edition, Java, virtualization, support costs, audits, compliance in SaaS, missing price holds, and changing bundles and metrics. Most of them come from contracts, installed features and audits, not from list prices. Each is explained below, with Oracle’s list prices of 15 September 2026 where they apply.

Oracle’s licensing terms for cloud and on-premises environments are complex and often unintuitive. Sourcing, procurement, vendor management and technology leaders need to know the main issues to avoid unexpected costs at renewals and first purchases. For the full cost picture, see Oracle licensing costs.

How we chose these ten issues

We worked with 39 Oracle customers between June 2023 and May 2024. Each had different challenges, and we normalized the issues they faced into the list below. Many of these engagements ran on, which kept the list current for us. The customers came from industries across India, the Middle East and Africa.

The ten issues

1. Oracle pushing against ULA certification

This may not sound like a licensing issue at first. But Oracle’s push to renew a ULA against the customer’s wishes and needs is made possible by license non-compliance allegations. Customers get frightened by Oracle’s stance and demands, and many end up accepting costly renewal proposals. Read how Oracle ULA certification works.

2. Use of unlicensed features in Oracle Database

This has long been Oracle’s strongest revenue channel. Oracle Database Enterprise Edition installs with almost all features, options and management packs. The responsibility for compliance sits with the customer, even when someone uses a feature without knowing it. On the 15 September 2026 price list, Diagnostics Pack is US$7,500 per processor and Tuning Pack is US$5,000 per processor, so one unnoticed pack on a few processors adds up fast. See how to disable Oracle options and packs.

3. Installing the wrong edition of WebLogic

Since 10g, WebLogic has had a single installer that contains the Basic, Standard, Enterprise and Suite editions. The recommended installation allows every feature. A customer can be out of compliance the moment the purchased product is installed.

4. Java

The Java license changes of January 2019 and the new employee metric of January 2023 created a new revenue stream for Oracle. Unless customers are very careful, it is hard to stay compliant with the many contract terms of Java licensing. The changes put almost every business on Oracle’s radar. Our timeline of Java license changes explains each step.

5. Virtualization

Oracle has long used its soft-partitioning and hard-partitioning definitions to press customers into paying heavy license fees. These are Oracle’s own definitions of virtualization configurations. The rules can be argued to be non-contractual, but Oracle’s sales staff insist on them. The cost of breaking these rules can increase license costs by 30 to 100 times what the actual usage would cost. See Oracle on VMware.

6. Support cost reduction

Customers in every industry want to cut their annual support costs (for the wider picture, see Oracle license optimization in 2026). The reasons are:

• Annual support costs have grown to unacceptable levels because of procurement and license management mistakes made over two decades or more.
• Customers do not see value for the money they pay. Third-party support firms often give better support at a fraction of the price.
• In the engagements we reviewed, Oracle was raising annual support fees by 6 to 8%. At the top of that range the fee doubles in nine years.

Oracle does not make support reduction easy. Under its support policies, all licenses of a program in a license set must be on the same support level, and ending support on part of an order means the remaining support is repriced. Talks about support cost can also drift into compliance questions, which makes dealing with Oracle messier. Read about third-party support for Oracle.

7. More license audits

We saw more Oracle audit activity, and it comes in two kinds.

• Soft audits are run by Oracle sales executives and look like a formal audit. The account executive tries to allege non-compliance or to learn about your deployments so as to generate extra revenue. Soft audits are a long-standing tactic, and we saw a big rise in them tied to Java demands.
• Formal audits come as written notice from Oracle License Management Services or from Oracle’s legal counsel. Oracle reserves the right to audit use of its software, to make sure customers do not use more licenses than they pay for.

If you receive either, read our guide to Oracle license audit defense.

8. Compliance issues in SaaS use

Many customers first believed that cloud would remove compliance concerns. It has not. Early users of Oracle Fusion Cloud services have already faced compliance issues from unauthorized use. They range from how users access the application by role and license metric, to seeded roles, double counting and third-party access.

9. Rate contracts and price holds

If you do not negotiate price caps, price holds or rate contracts, costs can rise sharply at renewal. Reducing your usage also does not reduce your prices. See Oracle contracts for what to look for.

10. Changing sales bundles and license metrics

Oracle changes its sales bundles and license SKUs often. In SaaS applications the metrics change constantly too. This leads to compliance issues and price increases. Oracle’s Fusion Cloud global price list shows how complex the SaaS license metrics are.

When customers come to us

• Oracle salespeople demand large license fees and threaten an audit.
• Oracle has sent a formal audit notice, or has finished running LMS scripts.
• Your Oracle ULA term is ending and you want to certify or renew.
• Oracle wants you to pay for Java.
• You plan a cloud migration and want to know how to use Oracle licenses.
• You pay very high support fees to Oracle.

How much can you save?

We have saved customers between 30% and 100% of potential license exposure during audit or ULA situations. On support, we have helped clients cut annual spend by 20% to 60%. See our Oracle cost reduction service, or the case studies page.

Questions we are asked about Oracle licensing costs

What are the best cost optimization strategies for Oracle Database licensing and support?

Remove the options and packs nobody uses, pick the metric that fits each system, move suitable databases to Standard Edition 2, run Oracle on fewer, dedicated hosts, and negotiate price holds before a renewal rather than at it. For stable systems that no longer need upgrades, compare third-party support. Before you drop licences to save support, check how Oracle reprices what remains. Our page on Oracle support costs explains how the bill is built.

Is Oracle Cloud cheaper for licence-heavy enterprise workloads?

For licences you bring yourself, usually yes. On Oracle Cloud one processor licence covers two OCPUs, which are two full cores. On AWS, Azure and Google Cloud it covers two vCPUs, which are usually one core, so the same workload needs twice the licences. Compute prices differ too, so compare both. Our guide to licensing Oracle in the cloud covers each provider, and the Oracle license cost guide has the prices.

How many processor licenses do I need?

Processor licenses are cores multiplied by the core factor, and fractions are rounded up. Intel and AMD server processors have a core factor of 0.5. Use the Oracle core factor table.