Contents
Key takeawaysHow licensing worksWhat it costs in 2026Enterprise Edition or SE2Named User Plus or processorDiagnostics and Tuning PacksLicensing on VMwareAWS, Azure and Google CloudWhat we see in reviewsWhat Oracle will sayContract terms to ask forWhat to do nextFAQOracle Database is priced on three decisions at once: the edition sets the unit price, the metric sets what you count, and options and packs add fees on that count. Then the infrastructure decides how many processors Oracle sees.
- Three decisions set the bill. Edition, metric and options each carry a price, and the hardware or cloud underneath decides how many processors Oracle counts.
- The editions count differently. Enterprise Edition is priced per processor after the core factor; SE2 per occupied socket, on servers with at most two sockets.
- Support outgrows the license. Support is charged every year on the net fee, so within five years it costs more than the license did.
- User minimums are floors. With 25 NUP per processor on Enterprise Edition, NUP only wins below about 50 users per processor.
- Packs are on by default. Diagnostics and Tuning are enabled in every Enterprise Edition database, and their usage history is what an audit prices.
- Infrastructure changes the count. VMware can turn a small VM into a cluster wide claim, and public clouds count vCPUs instead of cores.
How does Oracle Database licensing work?
You license each Oracle Database installation on three axes at once, and an error on any one of them becomes an audit finding. The edition sets the price per unit and the hardware you may use. The metric sets what you count, and options and packs add fees on that count.
- Edition. Enterprise Edition or Standard Edition 2, which fixes the unit price, the hardware ceiling and whether options can be bought at all.
- Metric. Processor, which covers unlimited users on the counted hardware, or Named User Plus, which counts people and devices subject to minimums.
- Options and packs. Priced additions to Enterprise Edition, licensed on the same metric and count as their database.
- Infrastructure. A physical server, a VMware cluster and a cloud instance each give the same workload a different count.
The first three are purchase decisions. The fourth sets the count twice, at deployment and again when Oracle measures. Mistakes tend to surface about two years later, priced at list, with back support attached.
How to Prepare for Your Oracle SaaS Negotiation
How much does an Oracle Database license cost in 2026?
Enterprise Edition lists at $47,500 per processor and Standard Edition 2 at $17,500 per occupied socket. Named User Plus costs $950 per user on Enterprise Edition and $350 on SE2. Annual support is 22 percent of the net license fee, every year.
| Product | Processor license | Named User Plus | Annual support per processor |
|---|---|---|---|
| Enterprise Edition | $47,500, counted as cores times the core factor | $950, minimum 25 per processor | $10,450 |
| Standard Edition 2 | $17,500 per occupied socket, cores ignored | $350, minimum 10 per server | $3,850 |
| Diagnostics Pack | $7,500 | $150 | $1,650 |
| Tuning Pack, requires Diagnostics Pack | $5,000 | $100 | $1,100 |
| Partitioning | $11,500 | $230 | $2,530 |
| Real Application Clusters | $23,000 | $460 | $5,060 |
Options and packs are licensed on the same metric and the full count of their database, so a pack on a 16 processor database needs 16 pack licenses.
What does support add over five years?
One Enterprise Edition processor at list carries $10,450 of support a year, so five years of support comes to $52,250, more than the $47,500 paid for the license itself.
Because support follows the net fee, every processor you avoid through edition choice or pack cleanup saves twice: once on the license and again every year on support.
Oracle CIO Guide
Edition, metric, pack and virtualization decisions for Oracle Database, with the negotiation sequence that follows.
Get the white paper →Should you choose Enterprise Edition or Standard Edition 2?
Choose Standard Edition 2 wherever the workload fits inside its limits and needs no Enterprise Edition feature. SE2 costs far less per unit and counts sockets instead of cores, so the gap widens every time chips gain cores.
| Term | Enterprise Edition | Standard Edition 2 |
|---|---|---|
| List price | $47,500 per processor, after the core factor | $17,500 per occupied socket, cores ignored |
| Hardware limit | None: any server, any scale | Servers with a maximum of two sockets, and 16 CPU threads per database at any time |
| Named User Plus minimum | 25 per processor | 10 per server |
| What you can add | The options and packs catalog, including RAC, Partitioning, Diagnostics and Tuning | Nothing: the engine alone, with no separately priced options |
A two socket server with 32 Intel cores is 16 processors at the 0.5 core factor, which lists at $760,000 on Enterprise Edition before any option. The same server lists at $35,000 on SE2, for a workload that fits.
Per unit, Enterprise Edition costs 2.7 times as much as SE2, and core counting multiplies that. Confirm a database needs an Enterprise Edition feature before paying for it. Our EE versus SE2 comparison sets out the fit test, and the SE2 licensing guide covers migration.
With no options catalog, an SE2 database cannot produce an unlicensed Diagnostics or Partitioning finding, and its pack access parameter defaults to NONE. Taking a database down to SE2 lowers the price and the audit risk in the same step.
When does SE2 stop being allowed?
- A server with more than two sockets. SE2 may only be licensed on servers with a maximum capacity of two sockets, so a four socket refresh rules it out.
- Sustained demand above 16 threads. Each SE2 database may use at most 16 CPU threads at any time, so larger workloads need splitting or Enterprise Edition.
- Clustering. From 19c, SE2 no longer includes Real Application Clusters; Standard Edition High Availability offers failover only.
- A gated feature. Partitioning, Advanced Security encryption, Active Data Guard and the management packs all require Enterprise Edition.
When is Named User Plus cheaper than processor licensing?
Named User Plus is cheaper when the real user population sits below about 50 users per processor on Enterprise Edition. That crossover is $47,500 divided by $950, and the minimums put a floor under the count.
Named User Plus licenses every person and device that uses the database, directly or through an application server, with a minimum of 25 per processor on Enterprise Edition (or the actual count, if greater) and 10 per server on SE2.
Worked example: one server, three user populations
Say you run Enterprise Edition on a server with 8 Intel cores. At the 0.5 core factor that is 4 processors, so processor licensing costs $190,000 at list and the Named User Plus floor is 100 users.
| Real users | NUP licensed | NUP cost | Processor cost | Cheaper metric |
|---|---|---|---|---|
| 12 | 100, the floor | $95,000 | $190,000 | Named User Plus |
| 200 | 200 | $190,000 | $190,000 | Either, this is the crossover |
| 300 | 300 | $285,000 | $190,000 | Processor |
The twelve users still license one hundred NUP, because below the floor you pay the floor. The crossover sits at 200 users, which is 50 per processor, and every user above it makes the processor metric cheaper.
Who counts as a named user?
- People behind the application. Oracle's multiplexing rule counts the users at the front end of any middleware, connection pool or application server, in full. An application with 2,000 staff connecting through one service account licenses 2,000 users.
- Devices. Oracle requires licenses for non human operated devices that access the database, such as sensors and bar code scanners.
- Growth. The metric that fit at deployment rarely fits by year five, so rerun the comparison per database at every renewal.
Our NUP versus processor crossover analysis works through larger servers and mixed populations, and the multiplexing guide shows how front end users are counted.
Why are Diagnostics and Tuning Packs the most common Oracle audit finding?
Enterprise Edition ships with both packs switched on. The CONTROL_MANAGEMENT_PACK_ACCESS parameter defaults to DIAGNOSTIC+TUNING, the pack screens sit one click away in Enterprise Manager, and the database records their use whether or not you own a license.
Usage lands in DBA_FEATURE_USAGE_STATISTICS, the view Oracle's measurement scripts read. It keeps a first and a last usage date, so a feature opened once, years ago, still shows as used. Unlicensed Diagnostics, Tuning and Partitioning use led the findings in our reviews and is the first line every audit prices.
What does an unlicensed pack finding cost?
Take a hypothetical Enterprise Edition server licensed for 16 processors, where the defaults stayed on and DBAs used AWR reports and the SQL Tuning Advisor for two years. The auditor prices both packs on all 16 processors, plus back support.
| Line | Calculation | Amount |
|---|---|---|
| Diagnostics Pack licenses | 16 x $7,500 | $120,000 |
| Tuning Pack licenses | 16 x $5,000 | $80,000 |
| Back support, two years | $200,000 x 22 percent x 2 | $88,000 |
| Total at list | $288,000 |
Settling by buying the packs also adds $44,000 of support every year after. Switching the parameter off stops new usage, but it does not erase the history already recorded.
How do you check your own pack and option usage?
- The parameter. Run SHOW PARAMETER control_management_pack_access on every Enterprise Edition database. Set it to NONE, or DIAGNOSTIC if you own only that pack, with ALTER SYSTEM at the container level. Put the setting in your build scripts too, or every new database inherits the default.
- The usage view. Query DBA_FEATURE_USAGE_STATISTICS for DETECTED_USAGES, FIRST_USAGE_DATE, LAST_USAGE_DATE and CURRENTLY_USED against each priced option.
- Oracle's own script. options_packs_usage_statistics.sql, from My Oracle Support note 1317265.1, maps feature usage to the option or pack it belongs to.
- Enterprise Manager. Check the Management Pack Access settings in Cloud Control so that packs you do not own are disabled for every target.
- Your entitlements. Reconcile the results against your ordering documents, database by database, and keep the dated output.
The license position guide walks through these checks, and the options and packs analysis sets out the rules pack by pack. For the packs alone, see our Diagnostics and Tuning Pack guide.
How does Oracle license databases on VMware?
Oracle treats VMware as soft partitioning, so it counts every physical core the database could run on, whatever the virtual machine is assigned. Its partitioning policy states that soft partitioning is not permitted as a means to determine or limit the number of licenses required.
Under modern vMotion scope that reach covers the cluster and, in Oracle's broadest readings, every host managed by the same vCenter. That is how a 4 core deployment becomes a 96 core claim: a database VM sized at 4 cores on a cluster of four hosts with 24 cores each. The cloud section below prices both counts.
What limits the VMware count?
- Dedicated clusters. Run Oracle on a cluster sized to the processors you own and used for nothing else.
- Physical separation. DRS affinity rules are settings an administrator can change, so pair them with storage and vMotion networks other clusters cannot reach.
- Approved hard partitioning. Oracle's policy accepts a short list of technologies for partial counting, including capped IBM LPARs, capped Solaris Zones, and Oracle Linux KVM and Oracle VM under its guidelines. VMware is not on the list.
- Contract wording. An ordering document that names the licensed hosts or cluster gives you a written boundary to count against when Oracle measures.
These choices are cheapest before the first VM goes live. The virtualization licensing guide covers each one.
Should you rely on the argument that the partitioning policy is not in your contract?
A common piece of advice says the partitioning policy sits outside your agreement, so you can license the VM alone and argue the point if Oracle audits. We would not rely on it.
The argument may hold on paper, but you would be making it during an audit, with a cluster wide number already on the table. Build the dedicated cluster, document it, and write the licensed hosts into your ordering document instead.
How is Oracle Database licensed in AWS, Azure and Google Cloud?
In Oracle's authorized cloud environments the core factor table does not apply, and Oracle counts vCPUs instead. Two vCPUs equal one processor license when multithreading is enabled, and one vCPU equals one license when it is not.
The authorized list covers Amazon EC2 and RDS, Microsoft Azure and Google Cloud Platform. SE2 has its own rules there: every four vCPUs, rounded up, count as one socket, SE2 instances are limited to eight vCPUs, and the NUP minimum is 10 per eight vCPUs.
| Where it runs | What Oracle counts | Processor licenses | License at list |
|---|---|---|---|
| Dedicated on premises server with 4 cores | 4 cores x 0.5 core factor | 2 | $95,000 |
| AWS EC2, 8 vCPUs with multithreading on | 8 vCPUs divided by 2 | 4 | $190,000 |
| VMware VM on a 96 core cluster | 96 cores x 0.5 core factor | 48 | $2,280,000 |
The same database carries three different counts, so workload placement is a licensing decision to price before you migrate. The cloud environments guide covers each provider's rules.
Where does a ULA change this?
An Unlimited License Agreement settles these counting questions for its term. The exposure returns at certification, when deployments are counted and fixed, so placement still shapes the exit. The ULA guide covers the exit arithmetic.
What have we seen in recent Oracle Database reviews?
Across roughly 35 to 50 Oracle Database environments I advised on or defended between 2024 and 2026, the first finding rarely sat where the client was looking.
- Unlicensed packs on 20 to 40 percent of databases. Diagnostics, Tuning or Partitioning usage was recorded without a license, mostly from defaults and exploration rather than deliberate use.
- One in three Enterprise Edition deployments used no Enterprise Edition feature. Those databases carried the 2.7 times edition premium plus the exposure of the options catalog, for a workload SE2 could run.
The organizations that held their position ran this review every year, before the renewal, with their own scripts.
A pack someone opened once in Enterprise Manager years ago still counts, because the audit reads the usage history and ignores intent.
What will Oracle's account team say, and how should you answer?
Expect a few familiar lines. Each has a reply that keeps the discussion on your data.
- "Enterprise Edition is the standard for production." Ask which Enterprise Edition features each database uses, and check the usage view yourself.
- "The packs show as used, so they are licensable." Ask for first and last usage dates per database. Settle where use was sustained, and push back where the record shows one session years ago.
- "Your whole VMware cluster needs licenses." Show the cluster design, the host inventory and the vMotion and storage boundaries, and ask Oracle to count against that documented boundary instead of the whole vCenter.
- "Take Oracle Cloud Infrastructure and the finding goes away." Ask for the settlement and the cloud offer as separate, separately priced documents.
What contract terms should you ask for?
Ask for terms that fix the count and the price in writing. Oracle may refuse some of them.
- A named environment for VMware. Define the licensed hosts or cluster in the ordering document, so the count is agreed in writing.
- A price hold on additional licenses. Ask for your current discount to apply to further processors and options for a fixed period, so growth is not bought at list.
- Protection from support repricing. Oracle's support policies let it reprice the remaining support when you drop part of an order. Ask for the right to reduce at renewal with support on the licenses you keep held at its current net rate.
- Audit procedure. Oracle's standard license agreement allows an audit on 45 days written notice. Keep that period, confirm that your staff run the scripts, and require findings in draft before any price is quoted.
What to do next
- Twelve months before renewal. Test every Enterprise Edition database against the Enterprise Edition feature list, and plan the one in three that may fit SE2 for the next renewal or true up.
- Nine months before. Run options_packs_usage_statistics.sql and the usage view on every database, and reconcile pack and option history against entitlements before any measurement does.
- Six months before. Rerun the Named User Plus and processor comparison per database at the real population, with the minimums applied.
- Before any infrastructure change. Fix the VMware count through dedicated clusters and physical separation, with contract wording to match.
- Before any migration. Price the same workload on premises, on VMware and in each cloud before you choose where it runs.
- Before you talk to Oracle. Bring your own numbers. Our Oracle practice and audit defense services run this review with you.
Want a second opinion on your Oracle position? Our Oracle licensing consultants are former Oracle insiders who now work only for buyers.
Frequently asked questions
How much does an Oracle Database license cost?
At list, Enterprise Edition is $47,500 per processor or $950 per named user, and Standard Edition 2 is $17,500 per socket or $350 per named user. A two socket, 16 core Intel server on Enterprise Edition is 8 processors, or $380,000 before options, plus 22 percent of the net fee each year for support.
What is the difference between Enterprise Edition and SE2 licensing?
Enterprise Edition counts cores after the core factor and can carry the priced options and packs. SE2 counts occupied sockets, runs only on servers with at most two sockets, caps each database at 16 threads, and cannot carry options, so an auditor has far less to find.
What are the Named User Plus minimums?
Enterprise Edition requires 25 NUP per processor or your actual user count, whichever is higher, and SE2 requires 10 per server. A four processor Enterprise Edition database used by twelve people therefore needs one hundred NUP, and users reaching it through middleware count in full.
Why are the Diagnostics and Tuning packs such a common audit finding?
They are enabled by default in Enterprise Edition, and the database keeps the usage history Oracle's scripts collect, even after use stops. In our baselines 20 to 40 percent of databases showed unlicensed pack usage. Set the access parameter in every build script, including builds from older images.
How does Oracle license databases on VMware?
Oracle counts every physical core the database VM could run on, which can mean the whole cluster or every host under the same vCenter. That is how a 4 core VM on a shared cluster can become a 96 core claim. Dedicated clusters and contract wording, settled before any audit, limit the count.
How does Oracle Database licensing change in the cloud?
In AWS, Azure and Google Cloud, Oracle ignores the core factor table and counts vCPUs: two per processor license with multithreading on, one with it off. The same workload can need twice as many licenses on EC2 as on a dedicated Intel server, so price placement before you migrate.
Can you cut Oracle Database support costs by dropping licenses?
You can, but the saving is usually smaller than the license count suggests. Terminate part of an order and Oracle reprices support on the remainder at current list minus its standard discount. Every license in a set must also share one support level, so plan reductions order by order before renewal.