Oracle license metrics. What each one actually counts.

Oracle prices the same software four different ways, and the metric on your ordering document decides the bill before any discount does. This page is a reference for the four that govern almost every Oracle contract: Named User Plus, Processor, Employee, and Application User.

Each one counts a different thing. Named User Plus counts people and devices, Processor counts cores, Employee counts a population that has nothing to do with usage, and Application User counts authorizations per module. Getting the minimum wrong costs more than getting the metric wrong.

Read it alongside the Oracle knowledge hub, the Oracle services practice, and the Vendor Shield subscription.

What does Named User Plus actually count?

Every individual you authorize to use the program, plus every non human operated device that can access it. Activity is irrelevant. Authorization is the trigger, and the count is taken against the servers the program is installed on.

The three counting rules that decide the number

• Authorization, not usage. A user who has not logged in for two years still counts while the authorization exists. Deprovisioning is a licensing activity, not just a security one.
• Non human operated devices count. A scheduler, a sensor, a till, or an interface that reaches the program on its own counts as a Named User Plus in addition to the people.
• Multiplexing is measured at the front end. Pooling users behind an application server, a portal or a middleware layer does not reduce the count. The count is taken at the point where the population is identifiable.

The minimums, which usually set the bill

When Named User Plus wins

When the population is small, countable and stable, and when it sits below the crossover point for that program. On the Database lines the crossover is arithmetic rather than opinion, because Oracle prices Named User Plus at a fixed fraction of the Processor price.

The full crossover derivation, including the list prices behind it, is on the Oracle Database licensing guide. The point for a metrics reference is narrower: check the minimum before you check the headcount, because the minimum wins more often than the headcount does.

What does the Processor metric count?

Cores, not people. Oracle counts all processors where the programs are installed or running, multiplies the physical cores by the published core factor, and rounds every fraction up to the next whole license.

The counting rule, in the order it is applied

1. Identify every server where the program is installed or running. Installed counts even when the workload is idle.
2. Count physical cores on those servers. Threads are not cores and do not change the count.
3. Multiply by the core factor for that chip from the Oracle Processor Core Factor Table.
4. Round fractions up, per server, then sum. Rounding at the estate level understates the requirement.

The factor is the part buyers get wrong most often, and it is the difference between a compliant estate and a seven figure finding. The detail sits in the Oracle core factor guide.

Standard Edition 2 counts sockets, not cores

• The unit is the occupied socket. The core factor table does not apply, so a high core socket costs the same as a low core one.
• Hard ceilings apply. Standard Edition 2 carries server and thread limits that Enterprise Edition does not, and exceeding them is a licensing breach rather than a performance problem.
• The Named User Plus alternative is per server. The 10 user minimum is applied server by server, so a wide estate of small servers accumulates minimums quickly.

When Processor wins

• The population is unknown or public. Internet facing systems, customer portals, and anything reachable by third party users cannot be counted reliably.
• The population is large relative to the cores. Above the crossover, Processor is cheaper and it ends the counting argument permanently.
• Devices dominate. Machine to machine estates accumulate Named User Plus counts that nobody can defend in an audit.
• Evidence is weak. If you cannot produce a defensible authorization list, Processor removes the burden of proof entirely.

What does the Employee metric count?

A population, not a user base. Oracle's Employee metric counts your full time, part time and temporary employees, plus the full time, part time and temporary staff of your agents, contractors, outsourcers and consultants who support your internal business operations.

Nothing in that definition refers to the software. The Java SE Universal Subscription moved to this metric in January 2023, and it is the reason Java exposure so often lands an order of magnitude above the first estimate.

Inside the count and outside it

Why the metric changes the shape of the decision

Because the count is fixed by your organization and not by your engineering choices. Reducing the number of servers running Java, or the number of developers, does not move the number at all.

• It is all or nothing. There is no partial subscription for the systems that need Oracle Java. The population is the population.
• It is tiered. Oracle publishes per employee per month rates that fall as the employee band rises, so the marginal cost per head drops while the total climbs.
• It is the mechanism, not the product. Oracle has been extending population based metrics beyond Java, which is a structural pricing shift rather than a Java story. That thread is picked up in the pricing metrics and bundling playbook.

The Java specific detail, including how to build a defensible employee count, sits in the Java SE Universal Subscription employee metric guide.

What does Application User count, and how do module metrics differ?

Named individuals authorized to use a specific application program, counted per module rather than per person. The applications estate then layers a second family of metrics on top that count business volume instead of people.

Per module, not per person

• One person, three modules, three licenses. Authorization is per program, so a finance manager touching Payables, Receivables and General Ledger needs an Application User license for each.
• Dormant accounts count. An account remains an authorization until it is deactivated. Leaver processes are a licensing control.
• Self service access is usually a different metric. Employee self service functions are typically licensed on an employee count rather than as Application Users, which is why the two counts never match.
• Read the module, not the suite. There is no single applications metric, and the suite name on the invoice tells you nothing about the counting rule.

The other applications metrics you will meet

Where the applications count drifts

Three places, and all three drift upward over time without anyone deciding anything.

• Leavers and movers. Accounts that were never deactivated, and users who changed roles and kept both sets of responsibilities.
• Integration and service accounts. Generic accounts used by interfaces, which are authorizations like any other.
• Responsibility creep. A responsibility added to a role for one project, then inherited by every new joiner in that role.

White Paper · Oracle

Oracle CIO Complete Playbook

The five year plan to control Oracle spend. Read it free.

Read the white paper

How do you tell which metric your order actually uses?

Read the ordering document, not the support renewal quote and not the current price list. The metric is a contractual term recorded per program line on the order that created the entitlement.

The five fields that decide it

1. The program name, written out in full. Options and packs appear as separate lines and carry their own entry.
2. The license metric column. This is the binding term. Renewal quotes abbreviate it and sometimes carry it forward incorrectly.
3. The licensed quantity. Read it against the minimum for that program, because a quantity at the minimum tells you the count was never headcount driven.
4. The referenced agreement and its date. The definitions that bind are the ones in force when the order was signed.
5. Any special terms or amendments. Negotiated definitions live here, and they override the standard ones for that order only.

Retired metric names that still bind

Older estates carry metrics Oracle no longer sells. They remain enforceable, and they cannot be interpreted using today's definitions.

• Named User, Named User Single Server and Named User Multi Server. Predecessors of Named User Plus with different counting rules and different minimums.
• Concurrent Device. Counted simultaneous connections rather than authorizations, which is a fundamentally different obligation.
• Universal Power Unit. Priced against processor performance ratings rather than core counts.
• Computer and Server based metrics. Tied to a named machine, which becomes a problem the moment the workload is virtualized or moved.

The rule most teams miss

The definition set travels with the order date. If your entitlement was created in 2011, the 2011 definitions apply to it, not the ones on Oracle's website today.

Keep the price list and agreement versions in force on each order date with the order itself. In an audit, that folder is the difference between arguing your position and accepting Oracle's.

Which metric wins, and when?

It depends on one question per metric, and none of them is about price. The reference below is the short version of a comparison worth running system by system.

What a metric switch can and cannot do

• It can move the bill materially where the system sits on the wrong side of the crossover for that program family.
• It cannot beat the minimum. Switching to Named User Plus on a large server lands you on the floor, not on your headcount.
• It usually needs Oracle's agreement and a new ordering document, so it belongs in a renewal or a wider transaction rather than in a support conversation.
• It does not apply retroactively. A switch fixes the forward position and leaves any historic gap exactly where it was.

Where the common advice on Oracle metrics is wrong

The standard advice is to pick Named User Plus whenever you can count your users, because per user pricing looks cheaper than per processor pricing. We disagree. Across the 40 to 50 metric reviews we ran in 2024 and 2025, the per processor minimum forced a count 25 to 40 percent above the actual population on low user, high core systems, and in several cases it landed at exactly half the Processor price no matter how few people used the system. The right first question is not how many users you have. It is how many Processor licenses the hardware implies, because that number sets the floor the user count is measured against.

What should a buyer do next?

1. Build the metric register. One row per program line, showing the metric, the quantity, the ordering document and its date.
2. Attach the definitions in force on each order date, not the current ones, and file them with the order.
3. Flag every retired metric in the register. Those lines need interpretation before they need optimization.
4. Compute the Processor implication first on every technology system, because it sets the Named User Plus floor.
5. Test both metrics per system, not per estate. The answer flips system by system and a single estate wide rule is always wrong somewhere.
6. Rebuild the employee count from payroll and vendor records, not from directory accounts, wherever an Employee metric applies.
7. Reconcile Application User counts to active accounts per module, and make deactivation part of the leaver process.
8. Schedule any metric conversion for a renewal or a wider transaction, since it needs a new ordering document to become real.

How Redress engages on metrics

Redress runs the metric register, the crossover comparison and the conversion analysis as an independent review, then defends the position through Vendor Shield. We do not resell Oracle and we do not implement it.

Read the Oracle services practice, the Oracle knowledge hub, and the Oracle support costs page, since every metric decision carries a 22 percent support tail behind it.

Frequently asked questions

What is the Oracle Named User Plus metric?

Named User Plus counts every individual authorized to use the program plus every non human operated device that can access it, whether or not anyone is actively using it. Authorization is the trigger, so dormant accounts count until they are removed, and multiplexing is measured at the front end rather than at the database.

What is the Named User Plus minimum per processor?

On Database Enterprise Edition it is 25 Named User Plus for every Processor license, calculated after the core factor. Standard Edition 2 uses 10 per server instead, and middleware programs carry their own program specific minimums. You license the higher of the real count and the minimum.

How does Oracle count a Processor license?

Physical cores on every server where the program is installed or running, multiplied by the core factor for that chip, with fractions rounded up per server. Threads do not count, idle installations still count, and Standard Edition 2 is counted per occupied socket with no core factor at all.

Does the Oracle employee metric count software users?

No. It counts your full time, part time and temporary employees plus the full time, part time and temporary staff of your agents, contractors, outsourcers and consultants who support your internal business operations. Whether any of them use the software is irrelevant to the count.

Are contractors included in the Oracle employee metric?

Yes, where they support your internal business operations. This is the single largest source of understatement we see, because contractor and outsourcer populations sit outside the HR system that most teams use to build the number. Build it from payroll plus vendor records instead.

How is Application User different from Named User Plus?

Application User is counted per application module rather than per program installation, so one person authorized on three modules consumes three licenses. Named User Plus also counts non human devices and carries per processor minimums, which Application User does not.

How do I find out which metric my Oracle order uses?

Read the license metric column on the ordering document that created the entitlement, program line by program line. Do not rely on the support renewal quote, which abbreviates the metric and can carry it forward incorrectly, and do not interpret an old order against today's price list definitions.

Can I change an Oracle license metric at renewal?

Sometimes, and it requires Oracle's agreement plus a new ordering document. A conversion fixes the forward position only, it does not repair a historic gap, and it cannot beat the minimum, so model the floor before you assume a switch will save money.