How an Oracle license bill is built in 2026. Five cost lines, each with its own metric and its own contract.

Oracle bills database, middleware, applications, Java and cloud on different metrics under different contract documents. The overspend we find most often comes from unmapped options, Named User Plus minimums and sizing to policy documents in place of what you signed.

An Oracle customer rarely pays one license bill. Database, middleware, applications, Java and cloud each run on their own metric, and each can sit under its own contract document. This guide sets the five lines side by side, prices the parts that grow fastest, and shows where buyers overpay.

How does Oracle licensing work across the five cost lines?

Oracle licensing works as five separate cost lines, each with its own metric and its own contract vehicle. Fixing the database line and leaving the other four alone deals with about a quarter of the problem, so the first job is to see all five at once.

Why does the contract vehicle matter as much as the metric?

Buyers tend to skip the last column. Each vehicle carries its own audit language, its own termination rights and its own definition of which subsidiaries count as you. Read each document on its own terms, even where two lines share a master agreement.

A Java subscription order may define the customer differently from the master agreement your database licenses sit under, and a cloud order can carry its own renewal terms. Our comparison of OMA, OLSA and OCA agreement structures shows how the older and newer paper differ.

Why doesn't what you learn on one line carry over to the next?

Each line counts in a different unit. On premises, the Processor metric multiplies physical cores by the core factor table: 0.5 for Intel, so a 32 core server needs 16 licenses after rounding up. Our core factor analysis works through the table chip by chip.

• Authorized clouds. On AWS, Azure and Google Cloud, Oracle counts vCPUs with no core factor at all: two vCPUs equal one Processor license where multithreading is on, one vCPU where it is off.
• Employee metrics. Java and several applications count people. That number changes only through the contract definition.

Should you license Oracle by Processor or by Named User Plus?

Processor licenses the hardware and Named User Plus licenses the people and devices. Processor suits large or unknown user populations and anything internet facing. Named User Plus suits small, known populations, but only above minimums that catch many buyers.

• Processor. Physical cores times the core factor, rounded up. No user counting at all.
• Named User Plus. Every human and every device authorized to access the database, whether or not they log in. Multiplexing through an application server or a connection pool reduces nothing; you count the people at the front end.
• Enterprise Edition minimum. 25 Named User Plus per Processor. A four Processor server needs 100 named users even if ten people log in.
• Standard Edition 2 minimum. 10 Named User Plus per server.

Why can a switch to Named User Plus never save more than half?

Oracle prices every database product on Named User Plus at one fiftieth of its Processor price. Enterprise Edition is $47,500 per Processor and $950 per named user, so the 25 user floor costs $23,750, exactly half a Processor license. Below the floor you pay for users you do not have; above 50 users per Processor, Processor becomes cheaper.

The table is arithmetic. In practice, small databases counted at the 25 per Processor floor, with fewer than ten real users, cost 2 to 5 times what their actual use justified. Model both metrics before you sign and put both in the ordering document as priced alternatives. Our NUP minimum examples cover more server sizes.

How much do Oracle Database options cost compared with the engine?

The six most common Enterprise Edition options list at $73,500 per Processor combined, a ratio of 1.55 to 1 against the $47,500 engine. On a 16 Processor server that is $1,176,000 of options on $760,000 of database, before a single user is added.

Each option also lists on Named User Plus at one fiftieth of its Processor price, so a metric change scales options and engine together. Options take the count of the database they extend. The database licensing reference covers the engine and option rules in full.

How do you find option usage before Oracle does?

Query DBA_FEATURE_USAGE_STATISTICS on every database and read the DETECTED_USAGES, FIRST_USAGE_DATE, LAST_USAGE_DATE and CURRENTLY_USED columns. Then confirm each hit against the objects in the table above. A single partitioned table or one AWR report pulled by a DBA is enough to put an option into an audit finding.

• Management packs. Check CONTROL_MANAGEMENT_PACK_ACCESS. On Enterprise Edition it defaults to DIAGNOSTIC+TUNING, which is how many buyers end up using packs they never bought. Our guide to setting that parameter explains the change.
• Partitioning. Look for application schemas that create partitioned tables on install. Usage records remain after the objects are dropped, so keep dated evidence of the cleanup.
• Compression and encryption. Basic table compression is included with Enterprise Edition. ADVANCED compression and encrypted tablespaces are not.

Why the engine discount is the wrong place to start

The usual advice is to open an Oracle negotiation by pushing for the deepest discount on Enterprise Edition. We start elsewhere. In our reviews, unmapped Partitioning or Diagnostics Pack usage added 10 to 20 percent to the compliance gap wherever it appeared, and a better engine discount leaves that exposure untouched.

Map option usage first, disable or remove what the business does not need, and agree the count before any price is discussed.

Are Oracle policy documents part of your contract?

No. The partitioning policy says on its face that it is for educational purposes only and may not be incorporated into any contract. Your ordering document and master agreement are the texts that govern, and pricing against anything else buys license you do not owe.

The core factor table sits in between. Your Processor definition refers to it, so the factor applies, but the table itself is a published document you never signed and Oracle updates it. Keep a dated copy of the version in force when each order was signed.

What does sizing to policy cost?

In our reviews, buyers who sized to Oracle policy documents over provisioned by 15 to 30 percent against what their signed agreements required. The usual cause is the partitioning policy and its treatment of VMware as soft partitioning. A buyer who accepts that view before reading the contract licenses hosts where Oracle never ran.

What does the Oracle audit clause allow?

The audit clause in the standard master agreement is one short paragraph. Oracle may audit on 45 days written notice, you agree to cooperate and give reasonable assistance and access to information, and the audit may not unreasonably interfere with your business. If it finds a shortfall, you pay within 30 days of written notice.

The clause names no tool, sets no method or deadline for the audit, and grants no right to your hypervisor inventory. Audit teams routinely ask for more than that. Our note on redlining the audit clause covers limits worth adding before you sign.

How are middleware, applications, Java and cloud licensed?

Each of the other four lines has its own counting rule and its own typical error. Middleware is most often missing from internal records, and Java is most often overcounted.

Middleware

WebLogic Server lists at $10,000 per Processor for Standard Edition and $25,000 for Enterprise Edition. Many Oracle applications ship with restricted use WebLogic rights that cover only that application. The moment anything else is deployed on or connects through that WebLogic instance, it needs full use licenses at those prices.

Across the environments we reviewed, middleware was absent from the internal license position more often than it was present. It was never absent from the audit scope.

Applications

E-Business Suite and the other application families are priced on application user, employee or module metrics under a separate applications price list. Cost follows how many people are licensed and how many modules are switched on. The EBS applications guide covers the user types and the module traps.

Java SE

The Java SE Universal Subscription is priced on every employee, not on Java users, from $15 per employee per month with lower tiers for larger organizations. The count reaches contractor and outsourcer staff who support your internal operations, so you negotiate the definition. The first counts buyers put forward ran 18 to 28 percent above what their HR records supported.

Say a company has 800 employees and its first draft counts 944, 18 percent more. At $15 a month, that is $169,920 a year against $144,000, or $25,920 a year paid for people who do not meet the definition.

Cloud and unlimited agreements

Oracle Cloud is bought as Universal Credits or run with your own licenses under BYOL. The cost risk is a commitment sized above what you draw. A ULA changes the arithmetic for every product it covers until certification fixes the counts you keep, so review any ULA before you model the other lines.

How do you reduce Oracle support costs?

You reduce support by reducing the licensed base, because Oracle charges annual support at 22 percent of the net license fee. Enterprise Edition support lists at $10,450 per Processor a year. Remove unused options and surplus capacity, and support falls with them.

End whole options where you can. Oracle's support policies allow it to reprice the licenses you keep when you terminate part of a license set, so cutting 4 of 16 Processors on one order may save less than a quarter of that order's support.

Where do Support Rewards fit?

Support Rewards is the one mechanism that lowers the support bill without shrinking the base. Eligible OCI consumption earns credit against technology support at 25 to 33 cents per dollar, the higher rate going to ULA customers.

What have we seen in recent Oracle license reviews?

Across roughly 35 to 45 Oracle environments I reviewed between 2024 and 2025, the median customer carried 25 to 35 percent more license than its signed contracts required. The surplus was never in one place, so a review of the database line alone missed most of it. Two findings came up more than any other.

• Unmapped options. 7 of 10 had option usage no one had mapped, most often Partitioning and Diagnostics Pack.
• Policy sizing. 6 of 10 had bought license they did not owe by sizing to policy documents instead of contracts.

The other patterns in this guide came from the same reviews: the Named User Plus floor on small databases, middleware missing from internal records, and Java counts above what HR records supported.

Write all five lines on one page, each with its metric and its contract, before you negotiate any one of them.

What will Oracle's account team say, and how should you answer?

Most Oracle sales and audit conversations return to a few familiar lines. Each has a factual reply that rests on your contract.

• "You need to license every host in the VMware cluster." Ask which clause in your signed agreement says so. The partitioning policy states it cannot be incorporated into a contract.
• "Feature usage shows Diagnostics Pack, so you owe it on every Processor." Ask for the first and last usage dates per database, and show whether the parameter default caused the use.
• "Moving to Named User Plus will cut your bill." The most it can save is half, and only where real users sit at or below 25 per Processor. Ask for both metrics priced in the same quote.
• "Support is a fixed percentage and cannot come down." Accept the rate, then list the options and Processors you are ending and ask in writing how the repricing policy applies to what remains.

Contract wording to ask for

1. Priced alternatives. Processor and Named User Plus prices for the same products in one ordering document, so a later switch is already priced.
2. A named customer definition. The legal entities covered, listed by name, so an acquisition does not expand scope without your consent.
3. Audit method. An agreed data collection method, with virtualization data limited to hosts where Oracle is installed or running.
4. Price holds. Unit prices for additional licenses held for a set period, so growth is not priced from list.
5. Java count date. The date and HR source used for the employee count, fixed in the order.

What to do next

1. This week. Write the five lines on one page, each with its metric and its contract vehicle. It is the most useful hour in any Oracle program.
2. Within a month. Run DBA_FEATURE_USAGE_STATISTICS on every database and check each hit against the recording objects, since unmapped Partitioning or Diagnostics use was the most common finding.
3. Before any count leaves the building. Size every count to your signed contracts and set the policy documents aside.
4. Before signing. Model both metrics with the minimums, and put both in the ordering document as priced alternatives.
5. At renewal. Cut support by cutting the base: end unused options and surplus capacity as whole license sets.
6. If an audit letter arrives. Read the audit clause in your own agreement first, then talk to the Oracle practice before you run any Oracle script.

Frequently asked questions