Two metrics. One defensible count.
Oracle Database is licensed on the Processor or Named User Plus metric, with a core factor table on premises and a separate virtual CPU rule in the cloud. The cost and the audit risk live in the separately licensed options and management packs, not the database itself.
Written by Fredrik Filipsson · Co Founder and Group CEO, ex Oracle · Updated January 2026 · Buyer side, independent
Executive Summary
The Oracle Database bill is set by the metric you pick and the options you switch on, not by the data. Enterprise Edition lists at 47,500 dollars per processor and Standard Edition 2 at 17,500 dollars per socket, but a single option such as Real Application Clusters adds another 23,000 dollars per processor and annual support runs at 22 percent of net license.
Across the reviews behind this pillar, the largest recoverable pool was options and management packs running with no business need, followed by processor licensing used where Named User Plus would have been cheaper, and full cluster counting on virtualized estates.
The deadline that matters is your next support renewal or audit notice. Whatever is enabled and unexamined rolls into another year at an uplifted price. Measure feature usage first, then negotiate.
Key takeaways
- Oracle Database licenses on two metrics, Processor and Named User Plus, and you choose the cheaper fit per database.
- The core factor table applies on premises only, where an Intel core carries a 0.5 factor.
- Enterprise Edition requires a minimum of 25 Named User Plus per Processor.
- Options and management packs are licensed separately on the same metric as the database.
- Partitioning, Tuning Pack, and Diagnostics are the most common unlicensed audit findings.
- VMware soft partitioning does not bound the licensed cores in Oracle's contractual view.
- Measure feature usage before any vendor conversation, never after.
What we saw across Oracle Database engagements in 2024 and 2025
Across roughly 40 to 50 Oracle Database licensing engagements Fredrik Filipsson reviewed in 2024 and 2025, the headline core count was almost never the real problem. The exposure sat in separately licensed options switched on by default. Buyers who measured feature usage first cut the opening audit claim by roughly a third. Three patterns recur:
- Diagnostics and Tuning Pack usage appeared in 7 out of 10 estates that believed they were clean.
- VMware cluster disputes added a claimed 2 to 6 times the cores the buyer expected to license.
- Self measurement before the vendor conversation cut the first audit claim by a median of 25 to 38 percent.
How does Oracle Database licensing actually work in 2026?
Oracle Database is licensed on one of two metrics, Processor or Named User Plus. Processor licensing counts cores adjusted by a core factor. Named User Plus counts the people and devices that access the database.
Both metrics are defined in the Oracle Database licensing guide and priced on the Oracle technology price list. The list price is a starting point, not a settlement.
How is the Processor metric counted?
Multiply physical cores by the core factor for that processor, then round up. An Intel core carries a factor of 0.5, so two cores need one Processor license for Enterprise Edition.
The factors are published in the Oracle processor core factor table. The table only applies on premises. In authorized cloud Oracle counts virtual CPUs under a separate policy.
When does Named User Plus win?
- Small, countable populations: a database used by 40 named staff is cheaper on Named User Plus.
- Minimums apply: Enterprise Edition requires at least 25 Named User Plus per Processor.
- Batch and devices count: non human devices that access the database also count as users.
The break even is exact. At 950 dollars per Named User Plus and 47,500 dollars per processor, the crossover sits at 50 countable users per processor. Below 50, Named User Plus is cheaper. Above it, buy the processor.
Named User Plus versus processor: the 50 user break even
Cost per Enterprise Edition processor as the user count rises. NUP at 950 dollars per user with a 25 user floor; processor flat at 47,500 dollars.
List prices: Oracle Technology Global Price List, 2026.
Oracle Database metric selection logic
| Scenario | Better metric | Why | Watch out |
|---|---|---|---|
| Public facing application | Processor | User population is unknown and large | Count every core behind the database |
| Internal app, 40 users | Named User Plus | Countable, below the Processor break even | 25 NUP per Processor minimum |
| Cloud migration | BYOL on vCPU | Lower infrastructure rate | Do not double count on premises |
| Disaster recovery standby | Depends on Data Guard role | Active standby needs a license | Passive failover has a ten day rule |
Which Oracle Database options and packs drive the real cost?
The base Enterprise Edition license is only the start. Options and management packs are licensed separately and on the same metric as the database they sit on. A fully optioned processor lists at more than two and a half times the bare engine.
Which options trigger the largest true ups?
- Partitioning: common in large schemas and frequently unlicensed when discovered.
- Diagnostics and Tuning Pack: enabled by default in many tools and easy to use without a license.
- Real Application Clusters: licensed on every node in the cluster.
- Advanced Security and Active Data Guard: often switched on during a project and never licensed.
The accidental use of Diagnostics and Tuning Pack is the most common audit finding we see. The feature usage views light up the moment a database administrator opens the wrong screen.
Where the spend hides: option list price per processor
Each option is licensed on top of the Enterprise Edition processor, on the same metric. List prices, Oracle technology price list 2026.
Benchmark context: Redress Compliance advisory engagement file, 2024 to 2025.
White Paper · Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
How does virtualization change Oracle Database licensing?
Oracle distinguishes hard partitioning from soft partitioning in its partitioning policy. Hard partitioning can bound the licensed cores. Soft partitioning, including most VMware configurations, does not in Oracle's contractual view.
Why is VMware the classic dispute?
Oracle treats a VMware cluster as capable of running the database on any host, so it argues every core in the cluster needs a license. Buyers dispute this with isolation evidence. The dispute is contractual, not technical.
How does cloud BYOL count cores?
In authorized cloud, Oracle counts two virtual CPUs as one Processor license when hyper threading is on. The core factor table does not apply. Map owned licenses to the vCPU envelope before you migrate.
What triggers an Oracle Database audit and how do you defend one?
Audits follow signals. A lapsed support contract, a cloud migration, a merger, or a sudden drop in spend all raise the chance of a formal review under the Oracle software investment guide terms.
What is the defense sequence?
- Run your own measurement with the scripts before Oracle does.
- Reconcile feature usage against entitlements and disable anything unlicensed.
- Control the data room. Provide what the contract requires, not the whole estate.
Where the common advice on Oracle Database licensing is wrong
The standard advice from resellers is to buy extra Processor licenses as a safety buffer so you never fail an audit. We disagree. In roughly seven out of ten estates Fredrik Filipsson reviewed, the buffer licenses sat idle while the real exposure was unlicensed options like Partitioning and Tuning Pack switched on by default. The buffer paid Oracle for capacity nobody used and did nothing for the actual risk. The buyer side move is to measure feature usage first, disable what you do not need, license only what you genuinely use, and hold the saved budget for the negotiation. Buffer buying treats the symptom and funds the vendor.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The Oracle Database license is the easy part. The cost lives in the options, the packs, and the virtualization argument. Measure before you negotiate, never after.
Recommendation
Measure the estate against the metric, the options, and the virtualization boundary before your next renewal, then act in renewal order. The renewal date is the lock point: options and metrics left unexamined roll into another year at an uplifted price.
- Run the harvest first. Pull dated feature usage, disable unused options and packs, and model the Customer Support Identifier repricing before cancelling any line.
- Right size, then renegotiate. Test the metric per database against the 50 user line, license virtualization to controlled hosts, and cap the renewal uplift in writing on the reduced base.
We are glad to tie a meaningful part of the fee to delivered value.
What to do next on this estate
Use this sequence. It works whether you are 60 days or 270 days from a renewal or audit.
- Run the Oracle measurement scripts yourself across every database instance.
- Reconcile feature usage views against your entitlements and disable anything unlicensed.
- Decide Processor versus Named User Plus per database on current population.
- Document the virtualization boundary with isolation evidence before any audit.
- Map owned licenses to the cloud vCPU envelope before migrating.
- Hold the corrected position and the saved budget for the negotiation.
Frequently asked questions
What are the two Oracle Database license metrics?
Oracle Database licenses on the Processor metric or the Named User Plus metric. Processor counts cores adjusted by a core factor. Named User Plus counts the people and devices that access the database. You choose the cheaper fit per database.
How does the Oracle core factor work?
The core factor adjusts the physical core count for Processor licensing on premises. An Intel core carries a factor of 0.5, so two cores require one Enterprise Edition Processor license. The factor table does not apply in authorized cloud.
What is the Named User Plus minimum?
Oracle Enterprise Edition requires a minimum of 25 Named User Plus per Processor. Below that floor you still pay for 25 per Processor, which sets the break even point against Processor licensing.
Which Oracle options cause the most audit findings?
Partitioning, the Diagnostics Pack, and the Tuning Pack are the most common findings. They are easy to enable by default in standard tools and are licensed separately on the same metric as the database.
How does VMware affect Oracle licensing?
Oracle treats most VMware configurations as soft partitioning, which does not bound the licensed cores in its contractual view. Oracle argues every core in a cluster that could run the database needs a license. Buyers dispute this with isolation evidence.
How is Oracle Database licensed in the cloud?
In authorized cloud, Oracle counts two virtual CPUs as one Processor license when hyper threading is on, and the core factor table does not apply. Bring Your Own License lets you migrate owned licenses to that vCPU envelope.
What triggers an Oracle Database audit?
Common triggers include a lapsed support contract, a cloud migration, a merger or acquisition, and a sharp drop in Oracle spend. Audits follow signals that the licensed footprint may have changed.
What is the first move when an Oracle audit lands?
Measure your own position before responding. Run the scripts, reconcile feature usage against entitlements, disable anything unlicensed, and control the data room so you provide only what the contract requires.
