Oracle license types under the License Definitions and Rules. The metric you count, and the grant you hold.

Every Oracle license has two parts: a metric that sets how many licenses you buy, and a grant that sets what you may do with them. Most buyers know their metric. Few have read their grant, which decides what the license is worth.

What are the Oracle license types?

Every Oracle license is defined by two things: a metric and a grant. The metric sets the quantity you buy, such as Processor or Named User Plus (NUP). The grant sets what you may do with that quantity, from Full Use for any internal purpose down to an Embedded license that only works inside a partner's product.

Both appear on the ordering document beside each program, usually in two or three words. Those few words on the grant can change what the license is worth by an order of magnitude, and they are the part of the contract most buyers have never read.

Where do you find the grant for each program?

The grant exists only on paper. It is not visible in the database, in Enterprise Manager or in your CMDB. It sits in three documents:

• The ordering document. The description line beside each program.
• The license schedule. The list attached to each support renewal, with program, metric, quantity and Customer Support Identifier (CSI).
• The incorporated definitions. The License Definitions and Rules and the policies the order names.

Buyers who never pulled this paper tend to run ASFU databases as if they were Full Use. The difference stays invisible until an audit prices it.

Which metrics does Oracle use to count licenses?

Technology products such as Oracle Database and WebLogic use two metrics: Processor and Named User Plus. Applications add eight Enterprise metrics, defined in Oracle's License Definitions and Rules, which count the size of the business instead of the deployment. The Oracle licensing guide maps which products use which metric.

How is the Processor metric counted?

For Enterprise Edition, multiply the physical cores by the factor in Oracle's core factor table. Intel and AMD x86 cores carry a factor of 0.5, so a 32 core x86 server needs 16 Processor licenses. Standard Edition 2 ignores the core table and counts each occupied socket as one Processor.

Who counts as a Named User Plus?

Every individual authorized to use the programs, whether or not they are active, plus every non human device that reaches the database, such as a sensor or a scanner. People behind a multiplexing front end count one by one, so a single pooled account still needs a license for each person using it.

When is Named User Plus cheaper than Processor licensing?

Below 50 users per Processor license. Enterprise Edition lists at $47,500 per Processor and $950 per Named User Plus on the technology price list, and $47,500 divided by $950 is exactly 50. Under that population NUP costs less. Above it, Processor does.

Small deployments also hit a floor. Enterprise Edition requires at least 25 NUP per Processor, and Oracle licenses whichever is higher, the floor or the real user count.

Why does the NUP floor apply after the core factor?

The floor is written per Processor license, and Processor licenses only exist once the core factor has been applied. The 32 core x86 server is 16 Processors, so its floor is 400 users.

Reading the floor per core gives 800, which doubles the minimum. On this server 800 also happens to be the breakeven, so the misreading makes NUP look pointless when it is often the cheaper choice. More cases sit in our NUP minimum examples and the crossover calculator.

A buyer who chose NUP at 30 users per Processor pays 60 percent over the Processor price once the population reaches 80. The overpayment also carries into support. At the 75 user row, annual support at 22 percent of the license fee runs $83,600 higher than it would on Processor licenses, every year the licenses stay on support.

How does Standard Edition 2 differ?

SE2 counts a Processor as an occupied socket, runs only on servers with at most 2 sockets, and caps each database at 16 CPU threads. Its NUP floor is 10 per server. Our SE2 licensing guide covers what happens when a workload outgrows the thread cap.

What does each Oracle grant allow, and what breaks it?

Each step down from Full Use removes rights and takes money off the price. You pay for the discount by accepting the restriction, and the restriction binds for as long as you hold the license.

• ASFU. The cheapest legitimate way to run Oracle Database under an ISV product, and the most common source of a compliance finding. See our ASFU guide.
• Embedded. One connection outside the partner product voids the discount, as the ESL guide explains.
• Hosting. The PAH guide covers what counts as your own application.
• Unlimited. The ULA lifecycle guide and the PULA guide cover scope, certification and exit.

How does an ASFU license break?

We see three patterns, and each one breaches the restriction on the day it happens:

1. A second reader. A reporting tool or a data warehouse extract is pointed at the ASFU schema.
2. A replaced application. The ISV product is retired, and the database keeps running under a new front end.
3. Custom tables. Someone adds tables for convenience, serving needs the named application does not have.

None of these requires deliberate misuse. They arrive as ordinary project work, so the grant check belongs in your change process as well as in audit preparation.

What does it cost to change the grant later?

The difference between the two list positions, applied to the quantity you run today. Your support base then rises to match the new license value, permanently. In our view it is the most expensive routine transaction in the Oracle catalog, and the cheapest time to settle the grant is at the original purchase.

The grant is two or three words on the ordering document, and those words decide what an audit can charge you for.

Are Oracle term licenses still worth buying?

Yes, for workloads with a firm end date within about four years, provided the product is still sold on term. Since September 1, 2020, Oracle has sold term licenses for on premises software only as a one year term, and only for specific Technology products such as Database Enterprise Edition, WebLogic Server Enterprise Edition and GoldenGate.

The one year term lists at 20 percent of the perpetual price. Support is charged on top at 22 percent of the perpetual list fee, so each year costs 42 percent of perpetual list in total.

How does a term compare with perpetual over the life of a workload?

Compare across the life of the workload, not the budget year. Perpetual plus five years of support at 22 percent comes to about 210 percent of list. Five consecutive one year terms also come to 210 percent, but you end with nothing, while the perpetual license is yours to keep with or without support.

The old five year term cost about 180 percent with five years of support, and renewing it once cost more than ten years of perpetual. The table also assumes Oracle keeps selling the same term at the same price each year, which the order does not promise.

A term fits audit settlements for usage that is ending, migration overlaps with a fixed cutover date and projects with a funded end date.

How do the Enterprise metrics in Oracle's License Definitions and Rules work?

They price applications off the size of the business. The License Definitions and Rules define eight Enterprise metrics, and none of them measures how many people use the software or how many servers run it. The bill follows acquisitions, growth and reorganizations and does not respond to usage.

• Financial size. $M in Revenue, $M Revenue Under Management, $M in Operating Budget and $M in Cost of Goods Sold. Where cost of goods sold is not known, the definition deems it 75 percent of revenue.
• Logistics. $M in Freight Under Management, measured as the total transportation value of tendered orders for all shipments in a calendar year.
• People. Employee, which covers full time, part time and temporary staff plus any agents, contractors and consultants who access, use or are tracked by the programs; FTE Student, where each part time student counts as 25 percent of a full time student; and Trainee.

With these metrics, almost all of the negotiation is about the written definition. Oracle's Java SE Universal Subscription showed this at scale: priced per employee, it counts staff and contractors whether or not they ever run Java. The definitions traps guide covers the wording to watch.

What should the order say about an Enterprise metric?

• The definition by date. Cite the version of the License Definitions and Rules in force on the order date.
• The measurement source. Name the figure, such as revenue in the audited annual report for a stated fiscal year.
• Acquisitions and divestitures. A grace period before an acquired company counts, and what happens to licenses and support when a unit is sold. See our assignment clause guide.

How does Oracle BYOL change the license count in the cloud?

The metric survives the migration, but the conversion changes. In Oracle's authorized cloud environments, Amazon Web Services, Microsoft Azure and Google Cloud, two vCPUs count as one Processor license when multithreading is enabled, and one vCPU counts as one Processor when it is not. The core factor table does not apply.

With multithreading on, the 32 core server from the worked example presents as 64 vCPUs, which is 32 Processor licenses in the cloud against 16 on premises. Size the instance to the workload before migrating. Our Oracle on Azure analysis and the cloud counting guide work through the rules.

What makes a license eligible for BYOL?

Active support on the licenses you bring. Amazon RDS requires BYOL licenses to carry Software Update License & Support, and Oracle's BYOL to PaaS terms on OCI require you to keep paying annual support. In close to a third of the cloud migrations we reviewed, eligibility was misjudged because support had lapsed on the owned licenses.

How do you check your own Oracle license position?

Start with the paper, then let each database report what it can. Your own systems give you a count before Oracle's scripts do, as long as you know what each source misses.

For an ASFU database, compare the programs and machines in V$SESSION with the accounts the named application uses; anything else is a second reader. Our compliance scripts guide covers what Oracle's own measurement scripts collect.

Why is the native count only a starting point?

The database measures sessions and accounts, while the NUP definition counts people and devices. Reconcile the figures with HR and identity records, and you have a count your team can explain line by line before Oracle produces its own.

What will Oracle's account team say about metrics and grants?

• "The ISV says reporting against the ASFU database is fine." Ask for that in writing from Oracle. The audit reads your ordering document, and the ISV's opinion does not change it.
• "Moving from NUP to Processor means buying Processor licenses at list." Ask for the retired NUP licenses as a credit in the same order, and compare the offer with five more years on NUP including support.
• "Your licenses are yours, so BYOL is covered." Check the CSI status in My Oracle Support first. RDS and OCI BYOL depend on live support, which ownership alone does not give you.
• "A term license settles this cheaply." Agree only if the usage has a firm end date within about four years and the product is on the term list. Past five years, price perpetual.

What have we seen in Oracle metric reviews in 2024 and 2025?

Across the 30 to 40 Oracle license reviews I led in 2024 and 2025, the metric had almost always been chosen years before the invoice that exposed it, usually by someone who had since left the company. Two results stood out:

• NUP that outgrew its breakeven. Buyers on Named User Plus whose populations grew past 50 per Processor overpaid 20 to 50 percent against a Processor fit. The usual history was a choice made at around 30 users per Processor and never revisited at 80.
• Drifted ULA certifications. Where deployment scope drifted during the term, about half of the certifications recovered far less value than the customer expected.

Why we do not treat the metric choice as permanent

The usual advice is to pick the metric carefully at purchase and then leave it alone, since Oracle makes changes expensive. We agree with the first half only.

In the reviews above, the cost came from populations and usage that moved on while the paperwork stayed the same. Re measure both every year, and set a review trigger below the breakeven, for example at 40 users per Processor, so there is time to negotiate a conversion credit.

What to do next

1. Pull the grant for every program. Record it beside the metric from the ordering documents and the license schedule.
2. Recount NUP populations. Compare each against the 50 user breakeven, with the 25 per Processor floor applied after the core factor.
3. Sweep ASFU databases. Look for second readers, replaced applications and custom tables.
4. Check support before any BYOL migration. Confirm the CSI is live and recount under the vCPU rules.
5. Test Enterprise metrics before renewal. Measure revenue, employees or budget against the exact definition on your order.
6. Repeat the review every year. Also run it before any audit, migration or acquisition. The Oracle practice runs the review with you.

Frequently asked questions