If you read nothing else
Oracle Named User Plus optimisation comes down to one rule the sales motion never volunteers: for Database Enterprise Edition you must license at least 25 Named User Plus per processor, counted after the Core Factor, no matter how few people actually use the database. On a 2-socket, 16-core Intel server that is a 400-NUP floor — about $380,000 at the 2026 list price of $950 per NUP. You optimise by right-sizing the hardware the database runs on, counting every human and non-human user defensibly, and switching to Processor licensing only where the user population genuinely exceeds the minimum.
This toolkit explains the metric in plain terms, walks the count step by step, and gives the buyer-side levers that cut a Named User Plus bill without creating an audit exposure. Every figure carries a source and a date.
Key takeaways
- Named User Plus is a per-person and per-device licence, not a usage meter — anyone or anything authorised to use the database needs a licence, regardless of how often they actually connect (Oracle licensing rules, 2026).
- Enterprise Edition carries a hard 25-NUP-per-processor minimum, applied after the Core Factor, which sets the real floor of the bill and is the single most common cause of over-licensing (Oracle licensing rules, 2026).
- List price is $950 per Named User Plus for Database Enterprise Edition, with annual support at 22% of net licence value, so a 400-NUP floor is roughly $380,000 in licence plus ~$84,000 a year in support before any discount (Oracle Technology Price List, 2026).
- Non-human operators count — but computer-to-computer batch and multiplexing front ends are the trap: Oracle requires you to count users at the multiplexing front end, not hide them behind a connection pool (Oracle License Definitions and Rules, 2026).
- Across 600+ Oracle engagements, right-sizing the hardware footprint cut the NUP minimum by 30–60% before a single user was removed, because the floor is driven by cores, not headcount (Oracle Licensing Experts engagement data, 2026).
Recommendations by role
A Named User Plus count is built, defended, and right-sized — not guessed. Here is what each owner does.
Database / Infrastructure Lead
- Map every Enterprise Edition database to its host's socket and core count — the NUP floor lives there, not in the user list.
- Consolidate low-user databases onto fewer, smaller cores to drop the per-processor minimum.
- Pin Core Factor per processor type so the floor is calculated correctly, not over-stated.
SAM / ITAM Manager
- Build a defensible user inventory: named humans plus every non-human account that touches the database directly.
- Document where computer-to-computer batch applies so you do not over-count integration users.
- Reconcile the user count against the per-processor minimum and license the higher of the two — knowingly.
Enterprise Architect
- Identify multiplexing front ends and count users there, before Oracle's LMS scripts do it for you.
- Flag any database where the true user population exceeds 25 per processor for a Processor-metric switch.
- Isolate Enterprise Edition options — Partitioning, Diagnostics Pack — that quietly add their own NUP minimums.
CFO / Procurement
- Price the NUP floor and its 22% support tail before renewal, not after the audit.
- Negotiate the discount on the licensed quantity, then hold the count flat as headcount grows.
- Treat any LMS "user review" as an audit and route it through independent advisors first.
The toolkit: how do you right-size a Named User Plus count?
Work these questions in order. The minimum almost always binds before the headcount does, so the hardware is where optimisation starts.
What exactly is a Named User Plus?
A Named User Plus is a licence required for each distinct individual authorised to access the Oracle program, plus each non-human-operated device that accesses it. The metric does not measure concurrent sessions, frequency, or actual use — a person who logs in once a year still needs a licence if they are authorised. That definitional point is why "we only have 50 active users" is never a complete answer to Oracle.
Count by entitlement, not activity. Disable and document access for users who genuinely no longer need the database before you certify a count — removing the authorisation is what removes the licence requirement.
How does the 25-per-processor minimum set the floor?
For Database Enterprise Edition, Oracle requires a minimum of 25 Named User Plus per processor, where "processor" is the licensable core count after the Core Factor Table. You calculate the processors the hardware would need, multiply by 25, and that is the floor — you license the higher of the floor or your actual user count. A server with two 16-core Intel processors is 32 cores × 0.5 Core Factor = 16 processors, so the NUP minimum is 16 × 25 = 400, even if only 30 people use the database.
Buying NUP for a small team on a large server is the most expensive mistake in Oracle licensing. If the per-processor minimum dwarfs your real users, you are paying for phantom licences — the fix is smaller cores, not more users.
How do you count non-human and integration users?
Non-human operators — batch jobs, integration accounts, monitoring agents, ETL tools — each count as one Named User Plus when they access the database directly. The exception that saves money is computer-to-computer batch: automated batching of data between machines is permitted and does not force you to count the individuals behind it. The line between a chargeable non-human account and an exempt batch process is where forensic counting earns its keep.
Ask Oracle to identify, in writing, exactly which integration and service accounts it considers chargeable Named Users — then test each against the computer-to-computer batch exception before conceding the count.
Why is multiplexing the most common over-count?
If multiplexing hardware or software — a TP monitor, a web server, a connection pool — sits between users and the database, Oracle requires you to count the users at the multiplexing front end, not the pooled connections at the back. Enterprises that assume a 20-connection pool means 20 users are setting up the single biggest Named User Plus dispute in an audit. The front-end population is the licensable number.
Do not present pooled database connections as your user count. Oracle's LMS scripts and contractual rules both push the count to the front end — under-counting here is the fastest route to a back-licence claim.
When should you switch from NUP to the Processor metric?
Named User Plus wins when the authorised population is small relative to cores; the Processor metric wins when users are many or uncountable — public-facing, internet-scale, or simply above 25 per processor. The break-even is the minimum itself: once your defensible user count climbs past 25 per processor, NUP stops saving money and Processor licensing caps the exposure. Model both for every Enterprise Edition database before renewal.
Where a database sits just above the break-even, use the Processor-vs-NUP choice as a negotiation lever — Oracle would rather discount the metric you prefer than lose the renewal to a re-architecture.
Strengths & cautions: NUP vs Processor
| Factor | Named User Plus | Processor |
|---|---|---|
| List price (EE) | $950 / NUP | $47,500 / processor |
| Minimum rule | 25 NUP / processor | None — count cores after Core Factor |
| Best fit | Small, countable user base | Large or public user base |
| Annual support | 22% of net NUP value | 22% of net processor value |
| Audit risk | Under-counted users / multiplexing | Core Factor & virtualisation scope |
The break-even is the minimum: at 25 users per processor the two metrics cost the same. Below it, NUP saves; above it, Processor caps the bill.
The cost case: the floor vs the right-size
Figure 1 — Named User Plus licence cost for 30 real users on a 2-socket, 16-core server, before and after right-sizing the hardware to 8 cores (illustrative, Oracle 2026 list at $950 / NUP).
The 30 actual users never bind — the floor does. Halving the licensable cores halves the 25-per-processor minimum, and with it the licence and the 22% support tail, with no change to the user base.
Decision matrix: which lever cuts your bill?
Figure 2 — The right optimisation move depends on whether the minimum or the headcount is binding.
Right-size the hardware
The 25-per-processor minimum is your whole bill. Consolidate onto fewer cores and the floor — and the support tail — falls with it. The highest-ROI lever on the board.
Switch to Processor
Once the defensible count passes 25 per processor, NUP stops saving. Move to the Processor metric to cap exposure and stop counting individual users.
Forensic-count and hold
You are near optimal. Lock a defensible count, document the batch and multiplexing exemptions, and resist Oracle's pressure to inflate it.
Processor only
Internet-facing or unbounded populations cannot be counted as Named Users. Processor licensing is the only defensible metric — price the cores, not the people.
In every quadrant, calculate the Core Factor first — an over-stated core count over-states the minimum and the whole bill.
Acronyms & key terms
- Named User Plus (NUP)
- Named User Plus is an Oracle licence required for each individual and each non-human device authorised to access the program, regardless of actual use.
- Processor metric
- The Processor metric licenses Oracle software by the host's core count after the Core Factor, with no user counting.
- Core Factor
- The Core Factor is the multiplier from Oracle's Core Factor Table that converts physical cores into licensable processors.
- 25-per-processor minimum
- The 25-per-processor minimum is Oracle's rule that Database Enterprise Edition must be licensed at no fewer than 25 NUP per processor.
- Multiplexing
- Multiplexing is any middleware tier — TP monitor, web server, connection pool — through which users reach the database; users are counted at its front end.
- Computer-to-computer batch
- Computer-to-computer batch is automated data transfer between machines, permitted without counting the individuals behind the process.
- Enterprise Edition (EE)
- Oracle Database Enterprise Edition is the full-feature database edition that carries the 25-per-processor NUP minimum.
- LMS
- License Management Services is Oracle's audit function, whose scripts measure deployed cores, users, and enabled options.
- Back-licence claim
- A back-licence claim is Oracle's demand for licences and back-dated support on usage it asserts you were not entitled to.
- Support uplift
- Support uplift is Oracle's 22% annual technical support charge, calculated on the net licence value of the metric you buy.
Frequently asked questions
What is Oracle Named User Plus optimisation?
Oracle Named User Plus optimisation is the buyer-side process of licensing a database to the lowest defensible Named User Plus count. Because Enterprise Edition enforces a 25-per-processor minimum, optimisation usually means right-sizing the hardware the database runs on, counting human and non-human users defensibly, and switching to the Processor metric only where the user population genuinely exceeds the minimum (Oracle licensing rules, 2026).
What is the Named User Plus minimum for Oracle Enterprise Edition?
Oracle Database Enterprise Edition must be licensed at a minimum of 25 Named User Plus per processor, calculated after the Core Factor Table is applied to the host's cores (Oracle licensing rules, 2026). A 2-socket, 16-core Intel server is 16 cores after the 0.5 Core Factor × 2 sockets... in practice 16 processors, giving a 400-NUP floor regardless of how few people use the database.
How much does a Named User Plus licence cost in 2026?
The 2026 Oracle Technology Price List shows Database Enterprise Edition at $950 per Named User Plus, with annual technical support at 22% of net licence value (Oracle Technology Price List, 2026). List price is Oracle's opening position; enterprises routinely negotiate 40–70% below list, but the per-processor minimum still sets the quantity you are discounting from.
Do batch jobs and service accounts need Named User Plus licences?
Non-human operators — batch jobs, integration accounts, monitoring agents — each count as one Named User Plus when they access the database directly. The exception is computer-to-computer batch: automated data transfer between machines is permitted without counting the individuals behind it (Oracle License Definitions and Rules, 2026). Each account should be tested against that exception before it is counted.
How does multiplexing affect the Named User Plus count?
When users reach the database through multiplexing hardware or software — a TP monitor, web server, or connection pool — Oracle requires you to count the users at the multiplexing front end, not the pooled connections. Presenting a 20-connection pool as 20 users is the single most common Named User Plus error and a frequent source of back-licence claims in audits.
When is the Processor metric cheaper than Named User Plus?
The Processor metric is cheaper once the defensible user population exceeds 25 per processor — the break-even is the minimum itself. Below that threshold, Named User Plus saves money; above it, or where users are public-facing and uncountable, Processor licensing caps the exposure. Every Enterprise Edition database should be modelled both ways before renewal.
How much can Named User Plus optimisation save?
Across 600+ Oracle engagements, right-sizing the hardware footprint cut the Named User Plus minimum by 30–60% before a single user was removed, because the floor is driven by cores rather than headcount (Oracle Licensing Experts engagement data, 2026). The saving compounds through the 22% annual support charged on the licensed quantity.
Methodology & sources
This toolkit combines Oracle's published licensing definitions and 2026 price list with Oracle Licensing Experts engagement data drawn from 600+ buyer-side Oracle engagements and $1.8B in Oracle spend advised. Benchmarks labelled "Oracle Licensing Experts" reflect anonymised outcomes across our license optimization work and are not attributable to any single client. Worked examples use Oracle's published $950 NUP list price and the 25-per-processor minimum; confirm your exact Core Factor and contract terms before acting.
Primary and authoritative sources cited:
- Oracle Technology Price List (oracle.com, 2026) — the $950 NUP and $47,500 processor list prices.
- Oracle License Definitions and Rules (oracle.com, 2026) — Named User Plus, multiplexing, and batch definitions.
- Oracle Processor Core Factor Table (oracle.com, 2026) — the multipliers that set the licensable processor count.
Download the PDF
Take the full Named User Plus Optimisation Toolkit with you — the metric explained, the worked floor calculation, and the right-sizing levers — in a board-ready PDF.
Request the PDF & a confidential licence review →Related white papers
The Oracle buyer's briefing
Quarterly Oracle audit and pricing benchmarks, written for buyers. No Oracle spin.