Oracle Database licensing, three axes, one bill
Oracle Database is priced on three independent axes, and a buyer has to get all three right at once: the edition sets the ceiling, the metric sets the counting rule, and the options and packs meter quietly underneath both. Miss any one and the finding arrives two years later, at list, with back support attached.
Prepared by Redress Compliance · August 6, 2026 · Oracle licensing advisory. Based on 35 to 50 database estates advised or defended 2024 to 2026.
Executive summary
Two editions, two counting rules. Enterprise Edition lists at $47,500 per processor, counted as cores times the core factor. Standard Edition 2 lists at $17,500 per occupied socket, cores ignored entirely, capped at two sockets per server.
Both carry support at 22 percent of net license fee, every year, which across a five year horizon quietly exceeds the license itself.
The metric minimums are floors, not guidance. Enterprise Edition requires 25 Named User Plus per processor; SE2 requires 10 per server. A four processor EE database with twelve real users still licenses one hundred NUP, and below the floor you pay the floor.
The NUP versus processor decision is arithmetic, not preference, and it flips at the minimums.
The packs are the number one finding. Diagnostics Pack and Tuning Pack ship enabled by default and record their own usage in the database whether or not you own them, which is why unentitled pack usage led the findings across our estates.
The usage history, not your intent, is what the measurement scripts read.
The infrastructure decides the count twice. On VMware, Oracle's soft partitioning position counts every core the database could be moved to, which is how a 4 core deployment becomes a 96 core claim.
At the cloud edge the core factor stops entirely: authorized clouds count vCPUs, two per processor license with hyperthreading on, and the same workload carries three different counts on premises, on VMware, and on EC2.
Edition first, the ceiling and the fence
| Enterprise Edition | Standard Edition 2 | |
|---|---|---|
| List price | $47,500 per processor, after the core factor | $17,500 per occupied socket, cores ignored |
| The hardware fence | None: any server, any scale | Two sockets per server maximum, and a 16 thread runtime cap |
| NUP minimum | 25 per processor | 10 per server |
| What it unlocks | The options and packs catalog: RAC, Partitioning, Diagnostics, Tuning, and the rest | The engine alone: no separately priced options, which is also its audit safety |
The edition decision is the largest single number in the estate: a two socket, 32 core server prices around $76,000 on EE at a 0.5 core factor before options, and $35,000 on SE2, for workloads that fit the fence.
The honest fit test and the migration mechanics sit in the EE versus SE2 comparison and the SE2 licensing guide, and in our estates one in three EE deployments carried no EE feature in use.
The metric, processor versus Named User Plus
Processor licensing covers unlimited users on the counted hardware; Named User Plus licenses the population, at $950 per user on EE list, subject to the minimums, and every human and device that touches the database directly or through middleware counts.
The crossover is mechanical: at the 25 NUP per processor minimum, populations above roughly 50 users per processor favor the processor metric, and the multiplexing rule means the population behind an application server counts in full.
The full decision math sits behind the NUP versus processor analysis.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
The packs, enabled by default, metered forever
Diagnostics Pack and Tuning Pack sit enabled by default in Enterprise Edition, their screens one click away in Enterprise Manager, and the database records every invocation in its own usage views, the same history the measurement scripts read, where a feature touched once, years ago, still counts.
Unentitled pack and option usage, Diagnostics, Tuning, and Partitioning leading, appeared on 20 to 40 percent of databases across our baselines, and it is the first finding every audit prices.
The control is documented in the license position guide: set the pack access controls, run the usage scripts internally on your own schedule, and reconcile the history against entitlements before anyone else does. The pack by pack rules sit behind the options and packs analysis.
The Oracle CIO complete playbook
The full estate strategy: edition and metric decisions, the pack controls, the virtualization position, the cloud counting rules, and the negotiation sequence across the Oracle relationship.
Get the white paper →VMware and the cloud edge, the count the infrastructure sets
Oracle treats VMware as soft partitioning: the licensable count is every core the database could run on, which under modern vMotion scope means clusters and, in Oracle's broadest readings, entire vCenter estates.
That is the mechanism that turns a 4 core deployment into a 96 core claim, and the defenses, host affinity, dedicated clusters, and contractual language, are architectural decisions with license consequences, worked in the virtualization licensing guide.
At the cloud edge the rules swap entirely: in the authorized clouds, AWS, Azure, and Google, the core factor table does not apply and Oracle counts vCPUs, two per processor license with hyperthreading enabled, one for one without.
The same database carries three different counts on premises, on VMware, and on EC2, and workload placement is therefore a licensing decision, per the cloud environments guide.
Estates at ULA scale trade these questions inside the unlimited agreement instead, with the exit math covered in the ULA guide.
What we saw across database estates, 2024 to 2026
Across roughly 35 to 50 Oracle Database estates Fredrik Filipsson advised or defended between 2024 and 2026, the first finding almost never sat where the buyer was looking:
Diagnostics, Tuning, or Partitioning usage recorded without entitlement, mostly defaults and exploration rather than intent.
Enterprise Edition deployments with no EE feature in use, carrying the 2.7x edition premium plus the options exposure.
The five year cost pattern completes the picture: at 22 percent support compounding on the license base, the recurring line overtakes the initial purchase, which is why the edition rightsizing and the pack cleanup pay twice, once on license and every year afterward on support.
The estates that held their position ran the three axis review annually, before the renewal, on their own scripts.
Your first five moves
- Test every EE database against the EE feature list, and move the one in three that fits SE2 at the next renewal or true up.
- Run the usage scripts internally and reconcile pack and option history against entitlements before any measurement does.
- Re run the NUP versus processor math per database at the real population, minimums applied; the metric that fit at deployment rarely fits at year five.
- Fix the virtualization position architecturally: dedicated clusters or host affinity with the contract language to match, before the vMotion scope becomes the claim.
- Price placement before migrating: the same workload counts differently on premises, on VMware, and in each cloud. The Oracle practice and audit defense services run the three axes with you.
Frequently asked questions
How much does an Oracle Database license cost?
Enterprise Edition lists at $47,500 per processor, counted as cores times the core factor, and Standard Edition 2 at $17,500 per occupied socket with a two socket cap.
Named User Plus runs $950 per user on EE with a 25 per processor minimum, and every license carries annual support at 22 percent of net fee.
What is the difference between Enterprise Edition and SE2 licensing?
The counting rule and the catalog. EE counts cores after the core factor and unlocks the separately priced options and packs; SE2 counts occupied sockets, ignores cores, caps at two sockets per server, and carries no options catalog, which also makes its audit surface materially smaller.
One in three EE deployments in our estates used no EE feature.
What are the Named User Plus minimums?
Twenty five NUP per processor on Enterprise Edition and 10 per server on SE2, and they are floors: a four processor EE database with twelve users licenses one hundred NUP.
The population also counts through middleware, so users behind an application server are counted in full under the multiplexing rule.
Why are the Diagnostics and Tuning packs such a common audit finding?
They ship enabled by default, their Enterprise Manager screens invite exploration, and the database records every invocation in usage views the measurement scripts read, where history counts even when current use stops.
Unentitled pack usage appeared on 20 to 40 percent of databases in our baselines, which is why pack access controls and internal script runs come first.
How does Oracle license databases on VMware?
Under Oracle's soft partitioning position, the count is every core the database could be moved to, which can reach the cluster or the vCenter estate, turning a 4 core deployment into a 96 core claim.
The defenses are architectural, dedicated clusters and host affinity, backed by contract language, decided before the audit rather than during it.
How does Oracle Database licensing change in the cloud?
In the authorized clouds the core factor table does not apply: Oracle counts vCPUs at two per processor license with hyperthreading enabled, one for one without.
The same workload therefore carries different counts on premises, on VMware, and on EC2 or Azure, which makes placement a licensing decision to price before migration.
