If you read nothing else
Oracle Database licensing turns on five things: the metric (Processor or Named User Plus), the Core Factor Table, the edition (Enterprise Edition at $47,500 per Processor versus Standard Edition 2 per socket), the priced options bolted onto EE, and how virtualization counts cores. The Processor metric counts every core where the software is installed and running, adjusted by core factor; NUP counts named humans and devices with a 25-per-Processor minimum on EE. Right-size against these rules and you cut the bill; ignore them and Oracle's LMS team writes the back-licence claim for you.
Oracle Database is licensed two ways — by Processor or by Named User Plus — and almost every compliance gap traces back to a misread of which metric applies, how the Core Factor Table adjusts the count, or which paid options are switched on. This masterclass walks the rules in the order they bite: the metrics, the editions, the options, the virtualization trap, and the support and cloud levers. It is written from the buyer side, by people who used to set these prices at Oracle, so you can defend your position before an audit forces the conversation.
Key takeaways
- Enterprise Edition lists at $47,500 per Processor. Oracle Database Enterprise Edition is $47,500 per Processor licence and $950 per Named User Plus on the 2026 Oracle Technology Price List, before any negotiated discount (Oracle Technology Price List, 2026).
- The Processor count runs through the Core Factor Table. Current Intel Xeon and AMD EPYC cores carry a 0.5 core factor, so a 32-core server needs 16 Processor licences; the factor ranges from 0.25 to 1.0 by chip family (Oracle Processor Core Factor Table, 2026).
- Enterprise Edition carries a 25-NUP-per-Processor minimum. Named User Plus licensing on Enterprise Edition requires at least 25 Named User Plus per Processor after the core-factor calculation — the floor that catches small user counts on big servers (Oracle Database Licensing, 2026).
- A fully optioned EE Processor can exceed $120,000. Database plus RAC ($23,000), Partitioning ($11,500), Diagnostics Pack ($7,500), Tuning Pack ($5,000) and the security and availability options lists above $120,000 per Processor — before 22% annual support (Oracle Technology Price List, 2026).
- VMware soft partitioning is the costliest trap. Across 600+ engagements, the single largest Oracle audit exposure is VMware soft partitioning, where Oracle claims every physical core in the cluster must be licensed — turning a small deployment into a multi-million-dollar back-licence claim (Oracle Licensing Experts engagement data, 2026).
01Recommendations by role
Oracle Database licensing is a measurement problem with a contract attached. Here is where each owner pushes first.
CIO / IT Director
- Demand a current, evidence-based licence position before any renewal or audit — you cannot negotiate what you have not counted.
- Challenge every Enterprise Edition deployment that does not need EE-only features; Standard Edition 2 or right-sized EE is often enough.
- Treat the Core Factor Table and the options inventory as board-level cost levers, not back-office detail.
Procurement / Vendor Management
- Anchor renewals to a forensic licence count, not Oracle's unverified entitlement record.
- Push back on net-new option pull-through — Oracle's quote often bundles options you never asked for.
- Negotiate the discount on the Processor list price, then hold the line on the 22% support uplift.
SAM / License Manager
- Map every database to its metric, edition, and core-factor-adjusted Processor count, server by server.
- Audit option usage forensically — Diagnostics and Tuning Pack are silently enabled in 40%+ of estates.
- Document virtualization boundaries so you can challenge a cluster-wide soft-partitioning claim with evidence.
CFO / Finance
- Model the 22% annual support stream as the real cost of Oracle ownership, not the one-time licence fee.
- Quantify the saving from retiring unused options and right-sizing EE to SE2 where features allow.
- Fund an independent licence review before the next audit — the average claim runs 3–5× what is actually owed.
02The rules, in the order they bite
How does the Oracle Processor metric count licences?
The Processor metric counts every processor core on which the Oracle Database software is installed and/or running, multiplied by the core factor from the Oracle Processor Core Factor Table. For current Intel Xeon and AMD EPYC chips the factor is 0.5, so two physical cores require one Processor licence; a 32-core server needs 16 Processor licences. The metric ignores how many users connect — it measures hardware capacity, not human headcount — which is why it is the default for web-facing or high-user databases where counting named users is impractical.
Always apply the core factor before you count. A buyer who licenses 32 cores at full count instead of 16 at the 0.5 factor doubles the bill. Check the Core Factor Table for your exact chip family — the factor ranges from 0.25 to 1.0.
When is Named User Plus cheaper than Processor?
Named User Plus is cheaper whenever you have a small, countable population of users and devices accessing a large server. NUP counts every human and every non-human-operated device authorised to use the database, subject to a minimum of 25 Named User Plus per Processor on Enterprise Edition after the core-factor calculation. For a database with 60 known users on a two-Processor server, NUP at $950 each beats two Processor licences at $47,500. Above roughly 500 users per Processor, the Processor metric almost always wins.
The 25-NUP-per-Processor minimum catches buyers who think a handful of users means a handful of licences. A two-Processor EE server with five users still requires 50 Named User Plus, not five — Oracle's LMS team counts the minimum, not your actual headcount.
Enterprise Edition or Standard Edition 2 — which do you need?
Standard Edition 2 is the right choice for smaller, simpler databases that fit its hard limits; Enterprise Edition is required for scale and for the EE-only options. SE2 runs only on servers with a maximum of two CPU sockets, is licensed per socket rather than per core, ignores the Core Factor Table, and caps each database at 16 CPU threads of processing. It cannot use RAC beyond a single restricted configuration, and it bars Partitioning, Active Data Guard, the diagnostic packs, and most options. If your workload fits inside two sockets and needs none of those features, SE2 saves a fortune; if it does not, you are in EE territory.
Before accepting an Enterprise Edition renewal, test every database against the SE2 limits. Workloads that grew up on EE out of habit — not need — can often drop to SE2, cutting the per-server licence cost by an order of magnitude. Re-platforming cost is usually a fraction of the licence saving.
Which Oracle Database options actually cost you money?
The priced options are licensed on the same metric as the database and add up fast: Real Application Clusters at $23,000 per Processor, Partitioning at $11,500, the Diagnostics Pack at $7,500, the Tuning Pack at $5,000, plus Advanced Security, Advanced Compression, Active Data Guard, and Multitenant beyond one pluggable database. A fully optioned Enterprise Edition Processor licence lists above $120,000. Because each option is metered separately, a single accidentally-enabled pack can create a compliance gap across every Processor it touches.
Across 600+ Oracle engagements, the Diagnostics Pack and Tuning Pack are found enabled and unlicensed in more than 40% of Enterprise Edition estates — usually switched on by default in Enterprise Manager and never licensed — Oracle Licensing Experts engagement data, 2026.
Why is VMware the biggest Oracle audit exposure?
VMware is the biggest exposure because Oracle treats it as soft partitioning, which under Oracle's policy does not limit the licensing boundary. Oracle's position is that you must license every physical core in every host the Oracle workload could run on — and with vMotion and shared storage, that can mean an entire vSphere cluster, not the handful of cores the database actually uses. A four-core database on a 200-core cluster becomes, in Oracle's claim, a 200-core licensing event. This is the single most common source of surprise audit findings, and it is contestable, not settled law.
"Show me the contractual clause — not the policy document — that requires licensing the entire cluster." Oracle's partitioning policy is not part of your licence agreement; the distinction between a policy and a contractual obligation is the ground on which a soft-partitioning claim is defended.
How do support and cloud BYOL change the maths?
Software Update Licence & Support is charged at 22% of the net licence fee every year, so a $1M licence purchase carries a $220,000 annual support bill that compounds for the life of the deployment — usually dwarfing the original licence over time. Cloud changes the counting, not the ownership: under Bring Your Own License you apply owned, supported licences to OCI, AWS, or Azure at the published cloud ratios — two vCPUs per Processor licence on a generic cloud, or richer ratios on Oracle's engineered cloud services. The licence you own is the asset; support and cloud are where the running cost is won or lost.
03Which edition and metric?
Choose your path
Large or web-facing workloads
Unknown or high user counts, EE-only options (RAC, Partitioning, Active Data Guard). Count cores × core factor. The default for mission-critical databases.
Small, countable user population
A known set of users and devices on a big server. $950 per Named User Plus, minimum 25 per Processor. Beats Processor below ~500 users per Processor.
Two sockets, no EE options
Fits within two CPU sockets, needs no Partitioning, Active Data Guard or packs. Licensed per socket, Core Factor ignored. An order of magnitude cheaper per server.
Migrating owned licences to cloud
Apply supported licences to OCI, AWS or Azure at published ratios — two vCPUs per Processor licence on generic cloud, richer ratios on Oracle engineered services.
Run this database by database, not estate-wide. The fastest savings come from finding EE workloads that fit inside SE2 and big servers where NUP beats Processor.
04Oracle Database editions & metrics, at a glance
| Edition / metric | 2026 list price | Key rule | Caution |
|---|---|---|---|
| EE · Processor | $47,500 / Processor | Cores × core factor (0.5 on Intel/AMD). | Options priced separately; soft-partitioning exposure. |
| EE · Named User Plus | $950 / NUP | Count users + devices; min 25 NUP per Processor. | Minimum catches small user counts on big servers. |
| Standard Edition 2 | Per socket (max 2) | Two sockets max; Core Factor ignored; 16-thread cap. | No Partitioning, Active Data Guard, packs; limited RAC. |
| RAC option (EE) | $23,000 / Processor | Same metric as the database. | Doubles the per-core cost of clustered nodes. |
| Partitioning option (EE) | $11,500 / Processor | Same metric as the database. | Often enabled in dev/test without a licence. |
05Acronyms & definitions
- Processor metric
- The Processor metric is Oracle's hardware-capacity licence unit — cores where the software is installed and/or running, multiplied by the core factor.
- Named User Plus (NUP)
- Named User Plus is Oracle's per-user licence metric — every human and non-human-operated device authorised to use the database, subject to per-Processor minimums.
- Core Factor Table
- The Core Factor Table is Oracle's published multiplier (0.25 to 1.0) that converts physical cores into Processor licences by chip family.
- Enterprise Edition (EE)
- Enterprise Edition is Oracle's full-feature database at $47,500 per Processor, supporting all priced options and unlimited scale.
- Standard Edition 2 (SE2)
- Standard Edition 2 is Oracle's lower-cost edition, licensed per socket on servers of up to two sockets, with no Core Factor and limited options.
- Soft partitioning
- Soft partitioning is virtualization Oracle does not recognise as limiting the licence boundary — including VMware — so the whole physical cluster may be claimed.
- Hard partitioning
- Hard partitioning is an Oracle-approved method (such as Oracle VM with CPU pinning or Solaris Zones) that does limit the licensable cores.
- RAC
- Real Application Clusters is an EE option for active-active clustering at $23,000 per Processor, licensed on every node.
- SULS / 22% support
- Software Update Licence & Support is Oracle's annual support fee, charged at 22% of the net licence value each year.
- BYOL
- Bring Your Own License is applying owned, supported Oracle licences to cloud at Oracle's published vCPU-to-Processor ratios.
06Frequently asked questions
How much does Oracle Database Enterprise Edition cost in 2026?
Oracle Database Enterprise Edition lists at $47,500 per Processor licence and $950 per Named User Plus on the 2026 Oracle Technology Price List, before any negotiated discount. Annual Software Update Licence & Support adds 22% of the net licence value every year. Priced options such as RAC and Partitioning are charged separately on the same metric, so a fully optioned Processor can exceed $120,000.
How does the Oracle Core Factor Table work?
The Core Factor Table is a published multiplier that converts physical cores into Processor licences by chip family. Current Intel Xeon and AMD EPYC cores carry a 0.5 factor, so two cores equal one Processor licence and a 32-core server needs 16 licences. The factor ranges from 0.25 to 1.0; IBM POWER chips, for example, carry 1.0. Always apply the factor before counting, or you overpay.
What is the difference between Processor and Named User Plus?
The Processor metric licenses hardware capacity — cores times core factor — regardless of how many users connect, and suits web-facing or high-user databases. Named User Plus licenses a countable population of users and devices, with a 25-per-Processor minimum on Enterprise Edition. NUP is cheaper for small, known user counts on large servers; Processor wins above roughly 500 users per Processor.
When should I use Standard Edition 2 instead of Enterprise Edition?
Use Standard Edition 2 when the workload fits within a two-socket server and needs none of the EE-only features — no Partitioning, Active Data Guard, diagnostic packs, or full RAC. SE2 is licensed per socket, ignores the Core Factor Table, and caps each database at 16 CPU threads. For workloads inside those limits it is an order of magnitude cheaper per server than Enterprise Edition.
Why is VMware a problem for Oracle licensing?
Oracle classes VMware as soft partitioning, which under its policy does not limit the licence boundary. Oracle's position is that every physical core the Oracle workload could run on must be licensed — potentially an entire vSphere cluster rather than the few cores the database uses. This is the most common surprise audit finding, but it rests on Oracle policy, not your contract, so it is defensible with evidence.
How much is Oracle Database annual support?
Oracle Software Update Licence & Support is charged at 22% of the net licence fee every year. A $1M licence purchase therefore carries a $220,000 annual support bill, which Oracle increases over time and which compounds to exceed the original licence cost. Reducing the support stream — by retiring shelfware or moving to third-party support — is often the largest available saving.
Can I move Oracle Database licences to the cloud?
Yes, through Bring Your Own License. You apply owned, supported Oracle licences to OCI, AWS, or Azure at Oracle's published ratios — generally two vCPUs per Processor licence on a generic cloud, with richer ratios on Oracle engineered services such as Exadata. BYOL reuses entitlement you already own rather than buying licence-included capacity, and is almost always the cheaper cloud path for a steady-state database.
07Methodology & sources
The benchmarks in this paper draw on Oracle Licensing Experts engagement data across 600+ Oracle licensing, audit-defence and optimization projects, 2026, combined with Oracle's published price and policy documentation. List prices are taken from the 2026 Oracle Technology Price List; core factors from the Oracle Processor Core Factor Table; metric definitions from the Oracle Database Licensing Information manual. Audit-exposure and option-usage figures are anonymised aggregates from buyer-side advisory work. We do not publish client names or fabricated deal counts.
Primary sources: Oracle, Oracle Processor Core Factor Table (Oracle, 2026); Oracle, Database Licensing (Oracle Database Licensing Information manual). See also our Oracle Database licensing guide and 2026 net-price benchmarks.
Download this white paper as a PDF
Keep the Oracle Database licensing rules — the metrics, Core Factor Table, EE-versus-SE2 limits, options pricing and the VMware trap — on hand for your next renewal or audit. Use your browser's print-to-PDF to save a clean copy.
Download / Print PDF →08Related white papers
Unsure what you really owe? Count it buyer-side first.
The metric, the Core Factor Table, the options inventory and the VMware boundary decide whether you are compliant or exposed. Our independent advisors build a forensic, evidence-based Oracle Database licence position and right-size the estate before Oracle's LMS team counts it for you — and the average claim runs 3–5× what is actually owed.
The buyer-side Oracle briefing
Monthly, independent intelligence on Oracle licensing, audits and cloud pricing — written for buyers, never for Oracle.
Prefer to talk? Request a free Oracle licensing briefing or see how we defend an Oracle LMS audit and run an independent compliance review.