Oracle Database EE licensing is the most expensive — and most audited — software-licensing decision most enterprises make. Enterprise Edition has no core caps, no socket limits, and no guardrails: you license every processor that runs it, every separately priced option stacks on top, and Oracle's LMS team treats every virtualized host as fair game. Get the metric wrong, or miss one partitioned table, and a routine measurement becomes a seven-figure back-license claim. This guide gives you the exact rules.
Short answer: Oracle Database Enterprise Edition is licensed by Processor or Named User Plus. Processor count = physical cores × the Oracle Core Factor (0.5 for most x86 chips). NUP carries a 25-per-processor minimum. Every separately priced option must cover the same processors as the database.
Oracle Database Enterprise Edition (EE) is the full-featured, top-tier edition of the Oracle Database, licensed per Processor or per Named User Plus with no hardware caps and a catalogue of separately priced add-on options. It is the only edition that supports high-end features such as Partitioning, Real Application Clusters (RAC), Active Data Guard, In-Memory, and the Diagnostics and Tuning Packs.
Unlike Standard Edition 2 (SE2) — which is capped at servers with a maximum of two CPU sockets and licensed by socket — Enterprise Edition has no socket or core ceiling. You can run it on a 4-socket, 256-core server, but you must license every processor under Oracle's rules. That open-endedness is exactly why EE is where Oracle's most valuable audit claims originate: there is no architectural limit protecting the buyer, only the contract and the metric you chose.
For the broader picture of how editions, metrics, and options fit together, our Oracle Database licensing guide is the pillar reference. This article focuses specifically on the Enterprise Edition rules.
EE is a platform, not a single license: Buying Enterprise Edition entitles you to the database engine and its built-in features only. Every option you enable — Partitioning, RAC, Advanced Security, In-Memory — is a separate paid license. Enabling one by accident is a compliance gap Oracle's scripts detect immediately.
Short answer: Oracle EE is licensed on exactly two metrics — Processor and Named User Plus (NUP). Processor licensing covers unlimited users on the licensed cores; NUP licenses countable named human and device users, subject to a 25-NUP-per-processor minimum. You choose one metric per database deployment.
The Processor metric is the default for any database with a large, growing, or uncountable user population — anything internet-facing, customer-facing, or feeding downstream systems. It licenses the hardware: every physical core running EE, adjusted by the Core Factor Table. Once licensed, an unlimited number of users can connect.
The Named User Plus metric licenses individual users and devices that access the database, whether directly or through middleware (Oracle's "multiplexing" rule means front-ending the database with an application server does not reduce the count). NUP is cheaper for small, well-defined user groups — internal tools, departmental systems — but only until you cross the break-even point. In our engagement data, the Processor metric becomes cheaper at roughly 50 users per processor (Oracle Licensing Experts, 2026); above that, Processor licensing almost always wins.
Choosing the metric is a negotiation lever, not a formality. We routinely re-model client estates to switch databases between metrics before a renewal, and the savings are frequently larger than any discount Oracle offers on price.
The Oracle Core Factor Table is the multiplier Oracle applies to physical core counts to derive the number of Processor licenses required. The formula is simple and absolute: physical cores × core factor = Processor licenses required, rounded up to the next whole number.
| Server | Physical Cores | Core Factor | Processor Licenses | List Cost (EE base) |
|---|---|---|---|---|
| 2-socket Intel Xeon, 16 cores | 16 | 0.5 | 8 | $380,000 |
| 2-socket Intel Xeon, 32 cores | 32 | 0.5 | 16 | $760,000 |
| 4-socket AMD EPYC, 96 cores | 96 | 0.5 | 48 | $2.28M |
| SPARC T-series, 32 cores | 32 | 0.5 | 16 | $760,000 |
The core factor for most current Intel and AMD x86 processors is 0.5, meaning one Processor license covers two physical cores. Older or specialised architectures carry different factors — some IBM Power chips are 1.0, certain SPARC chips 0.25 or 0.5. The authoritative reference is the Oracle Core Factor Table, and applying it correctly is one of the most common places LMS overclaims: counting hyperthreads as cores, or ignoring the factor entirely, inflates the required quantity. Always verify the factor against the published table before accepting any Oracle measurement.
Short answer: The Named User Plus minimum for Oracle Enterprise Edition is 25 NUP per processor. Oracle requires you to license the greater of your actual user count or 25 × the processor count. A two-processor server must carry at least 50 NUP even if only ten people use it.
A Named User Plus is any individual or device authorised to access the Oracle Database, counted regardless of whether they are actively using it. The 25-per-processor floor exists to stop buyers from licensing a powerful server for a handful of users and then quietly scaling usage. Crucially, the processor count in that formula uses the same core-factor math as Processor licensing — so a 32-core x86 server (16 processors) carries a minimum of 16 × 25 = 400 NUP, irrespective of how many people log in.
This minimum is the trap that turns "cheap" NUP licensing expensive. Buyers select NUP to save money on a low-user system, then discover the processor-derived floor is higher than their headcount. Before committing to NUP, model both metrics against the actual hardware. Our license optimization service runs this calculation across the whole estate so the metric choice is evidence-based, not guesswork.
Oracle Database Enterprise Edition lists at approximately $47,500 per Processor or $950 per Named User Plus, plus 22% of net license value in annual support (Oracle Technology Price List, 2026). Support is the part buyers underestimate: at 22% per year, a license costs more in cumulative support than its purchase price within roughly five years, and Oracle's support repricing rules make it difficult to drop support on part of an estate without penalty.
Negotiated discounts on the base license commonly reach 40–70% off list for meaningful volumes, but support is calculated on the discounted net value and then escalates annually. That is why the support line — not the license line — is where independent advisors find the durable savings, whether through support cost reduction or, in the right cases, certified third-party support. The list price is the start of the negotiation, never the number you should pay.
Our former-Oracle negotiators benchmark your EE pricing against what comparable enterprises actually pay — then build the evidence base to close the gap. 100% buyer-side.
Yes — and this is the single most expensive misunderstanding in Enterprise Edition licensing. An Oracle Database option is a separately licensed feature that runs only on EE and must be licensed on the same metric, and for the same processor or NUP count, as the underlying database. Buying EE does not entitle you to any of them.
| Option | List Price / Processor | What Triggers the License |
|---|---|---|
| Partitioning | $23,000 | Any partitioned table, index, or IOT exists in the database |
| Real Application Clusters (RAC) | $23,000 | Database runs across more than one clustered node |
| Active Data Guard | $11,500 | Standby opened read-only or used for real-time apply |
| Multitenant | $17,500 | More than the free limit of pluggable databases per container |
| Diagnostics Pack | $7,500 | AWR / ADDM access, including via Enterprise Manager |
| Tuning Pack | $5,000 | SQL Tuning Advisor or SQL Access Advisor usage (requires Diagnostics Pack) |
| Advanced Security | $15,000 | Transparent Data Encryption (TDE) or data redaction enabled |
| In-Memory | $23,000 | Any object populated into the In-Memory column store |
The danger is that most of these options enable silently. Transparent Data Encryption is a single ALTER away from triggering Advanced Security. Querying an AWR report through Enterprise Manager triggers Diagnostics Pack. A DBA partitions a large table for performance and creates a Partitioning requirement no one approved. Oracle's LMS audit scripts read DBA_FEATURE_USAGE_STATISTICS and V$OPTION to surface every option that has ever been touched. For the deepest treatment of the most common trap, see our Oracle Partitioning option licensing guide.
Oracle classifies VMware vSphere as "soft partitioning" and does not accept it as a boundary for licensing. Oracle's audit position is that any physical host an Enterprise Edition virtual machine could run on must be fully licensed for EE and every enabled option — not just the hosts it currently runs on. With vMotion and clustering, that quickly expands to an entire vCenter.
The practical effect is brutal: a single EE VM pinned to a small cluster can, under Oracle's interpretation, require licensing for every core in that cluster. This is the largest single source of EE back-license claims we see. The defence is architectural and evidentiary — isolating Oracle workloads onto dedicated, properly licensed clusters with documented affinity controls, and challenging Oracle's claim that soft partitioning has no contractual standing. Our Oracle audit defense team has repeatedly narrowed VMware-based claims by forcing Oracle to substantiate the "could run anywhere" assertion against the actual contract terms and documented configuration.
Do not run LMS scripts on a virtualized estate without advice: The output will enumerate every host in the cluster and hand Oracle the worst-case processor count. A documented client engagement cut a VMware-driven EE claim by more than $4M by re-scoping the measurement to the contractually licensable hosts before any data was submitted.
Right-sizing Enterprise Edition is the process of matching entitlements to genuine technical need — and it is where the money is. The disciplined sequence we follow on every engagement is:
DBA_FEATURE_USAGE_STATISTICS across production and non-production.Done forensically, right-sizing routinely removes 20–40% of an EE estate's annual cost before any price negotiation begins. The discipline is the deliverable — Oracle's pricing only ever moves when you can prove, line by line, what you actually need.
Oracle Database Enterprise Edition is licensed by one of two metrics: Processor or Named User Plus (NUP). Processor licensing counts physical cores multiplied by the Oracle Core Factor (0.5 for most x86 chips). NUP counts named human and device users, with a minimum of 25 NUP per processor. You pick one metric per deployment.
Enterprise Edition requires a minimum of 25 Named User Plus per processor. The processor figure uses core-factor math, so a 32-core x86 server (16 processors) carries a 400-NUP minimum regardless of headcount. You license the greater of actual users or the processor-derived minimum.
Enterprise Edition lists at roughly $47,500 per processor or $950 per Named User Plus, plus 22% annual support (Oracle Technology Price List, 2026). Separately licensed options such as Partitioning, RAC, and Diagnostics Pack add cost on top. Negotiated discounts of 40–70% off list are common at volume.
Processor licensing covers unlimited users on the licensed cores and suits internet-facing or large user populations. NUP is cheaper for small, countable groups but carries the 25-NUP-per-processor minimum. In our engagement data the break-even is roughly 50 users per processor; above that, Processor licensing wins (Oracle Licensing Experts, 2026).
Yes. Options including Partitioning, RAC, Active Data Guard, Multitenant beyond the free PDB limit, Diagnostics Pack, Tuning Pack, Advanced Security, and In-Memory are licensed separately on the same metric as the database, and must cover the same processor or NUP count. Buying EE alone does not entitle you to any option.
Oracle treats VMware as soft partitioning and does not accept it as a licensing boundary. Its audit position is that every physical host an EE VM could migrate to — across the cluster or vCenter — must be fully licensed. This is the largest single source of EE back-license claims and is challengeable with the right evidence.
Every Oracle Database edition, metric, and option compliance trap — written by former Oracle insiders for IT and procurement teams.
Weekly briefing on Oracle audit tactics, license changes, and negotiation intelligence — read by 2,000+ Oracle stakeholders at Fortune 500 enterprises.
Independent. Buyer-side. Not affiliated with Oracle Corporation.
25+ years · 600+ engagements · $1.8B Oracle spend advised · 38% avg cost reduction · 100% buyer-side · former Oracle insiders
Before Oracle's LMS team measures your Enterprise Edition estate, a forensic review identifies every processor, option, and virtualization exposure — and gives you the evidence base to right-size or defend.
Not affiliated with Oracle Corporation. 100% independent, buyer-side advisory.