Contents
Key takeawaysPrice list by lineSE2 versus Enterprise EditionWhich documents bindCommon pricing errorsChecking your usageOracle's lines and repliesWhat we saw in 2024 and 2025What to do nextFAQEnterprise Edition lists at $47,500 per processor and Standard Edition 2 at $17,500, yet about two thirds of typical spend sits in options and packs. Most overstated bills trace back to a price applied to the wrong line.
- One ratio covers every line. Named User Plus costs exactly 1/50 of the processor price on both editions and on every option and pack.
- The minimums set the floor. Enterprise Edition needs at least 25 Named User Plus per processor and SE2 needs 10 per server, and above 50 users per processor the processor metric is cheaper.
- SE2 counts sockets. An occupied SE2 socket is one license whatever its core count, while Enterprise Edition multiplies cores by the core factor.
- Three of eight documents bind. The ordering document, master agreement and support policies are contract, while the partitioning and cloud policies usually sit outside what you signed.
- Budgets carry free and mispriced lines. Spatial and Graph and Advanced Analytics have been included since 2019, and only three current option lines list at $23,000 per processor.
- Support compounds every error. Support is charged each year on the original net fee, passes the license cost within five years and reprices when you drop licenses.
What does an Oracle Database license cost on the current price list?
Enterprise Edition lists at $47,500 per processor or $950 per Named User Plus. Standard Edition 2 lists at $17,500 per processor, which for SE2 means per occupied socket, or $350 per Named User Plus. Personal Edition is sold only by Named User Plus, at $460.
Options and packs are priced on top of Enterprise Edition, on the same metric and count as the base license. Our technology price list guide covers the rest of Oracle's technology catalog.
| Line | Type | Per processor | Per Named User Plus |
|---|---|---|---|
| Enterprise Edition | Edition | $47,500 | $950 |
| Standard Edition 2 | Edition | $17,500 per socket | $350 |
| Personal Edition | Edition | Not offered | $460 |
| Multitenant | Option | $17,500 | $350 |
| Real Application Clusters | Option | $23,000 | $460 |
| Real Application Clusters One Node | Option | $10,000 | $200 |
| Active Data Guard | Option | $11,500 | $230 |
| Partitioning | Option | $11,500 | $230 |
| Real Application Testing | Option | $11,500 | $230 |
| Advanced Compression | Option | $11,500 | $230 |
| Advanced Security | Option | $15,000 | $300 |
| Label Security | Option | $11,500 | $230 |
| Database Vault | Option | $11,500 | $230 |
| TimesTen Application-Tier Database Cache | Option | $23,000 | $460 |
| Database In-Memory | Option | $23,000 | $460 |
| Diagnostics Pack | Pack | $7,500 | $150 |
| Tuning Pack | Pack | $5,000 | $100 |
| Database Lifecycle Management Pack | Pack | $12,000 | $240 |
| Data Masking and Subsetting Pack | Pack | $11,500 | $230 |
| Cloud Management Pack for Oracle Database | Pack | $7,500 | $150 |
How does the Named User Plus price compare with the processor price?
Oracle prices Named User Plus at exactly 1/50 of the processor price on every Database line, both editions, options and packs included. Per processor, Named User Plus is cheaper while fewer than 50 users sit behind that processor.
The minimums set the floor. Enterprise Edition requires 25 Named User Plus per processor, or the real user count if that is higher, and SE2 requires 10 per server. On an 8 processor Enterprise Edition server the floor is 200 users, $190,000 against $380,000 for processor licenses.
- Up to 400 users on that server. Named User Plus is cheaper, and you pay for at least 200.
- Past 400 users. Processor licensing is cheaper.
- Web applications and systems fed by other applications. These usually belong on processor licenses, because Oracle counts every person at the front of any multiplexing layer, and that number is hard to prove.
Where does most Oracle Database spend actually go?
About two thirds of the spend on a typical Oracle Database account sits in the options and packs on top of the base edition. One processor carrying Real Application Clusters, Partitioning, Active Data Guard, Diagnostics and Tuning adds $58,500 of options and packs, more than the $47,500 base costs.
How to Negotiate Your Oracle SaaS Renewal: The Five Moves at the Table
How do Standard Edition 2 and Enterprise Edition licensing differ?
SE2 is cheaper, capped in hardware and counted per socket. Enterprise Edition has no socket cap, carries the full option catalog and is counted per core through the core factor. The unit price gap is 2.7 times on either metric.
| Capability | Standard Edition 2 | Enterprise Edition |
|---|---|---|
| Maximum sockets | 2 per server, 16 thread cap per database | Unlimited |
| RAC, Partitioning, Active Data Guard, Compression | Not available | Priced options |
| Diagnostics and Tuning packs | Not available | Priced packs |
| List per processor | $17,500 | $47,500 |
| List per Named User Plus | $350 | $950 |
| Named User Plus minimum | 10 per server | 25 per processor |
| Counting rule | One occupied socket counts as one license | Cores times the core factor, rounded up |
The counting rule is the largest structural difference between the editions. Take a two socket Intel server with 24 cores per socket. Enterprise Edition needs 48 cores times 0.5, or 24 processor licenses, $1,140,000 at list. SE2 needs two socket licenses, $35,000, though each SE2 database may use only 16 CPU threads.
Our Enterprise Edition versus SE2 comparison and SE2 licensing guide cover the trade offs by workload.
How is a processor counted on premises?
Multiply the physical cores by the factor in Oracle's Processor Core Factor Table and round any fraction up to the next whole number. Current Intel Xeon and AMD EPYC chips mostly carry 0.5, IBM POWER carries 1.0, and any multicore chip not listed defaults to 1.0. Our core factor guide lists the exceptions.
Under virtualization the count depends on whether Oracle accepts the technology as hard partitioning. Its partitioning positions name VMware as soft partitioning, which is where the arguments about licensing a whole cluster begin.
How are vCPUs counted in AWS, Azure and Google Cloud?
Oracle's cloud policy counts two vCPUs as one processor license when multithreading is enabled, and one vCPU as one license when it is not. The core factor table does not apply, whatever chip is underneath, and the policy now lists Google Cloud beside AWS and Azure.
For SE2, every 4 vCPUs count as one socket, and SE2 is allowed only on instances of up to 8 vCPUs, with a minimum of 10 Named User Plus per 8 vCPUs. Our vCPU rules page works through common instance sizes.
What about Personal Edition and Oracle Database Free?
Personal Edition is licensed per Named User Plus only and includes every Enterprise Edition component and every option except RAC and RAC One Node. Management packs cannot be used with it. That breadth is why it turns up as an audit finding on developer laptops, one licensed user per install.
- Oracle Database Free. The successor to Express Edition costs nothing and is capped at 2 CPUs for foreground processes, 2 GB of RAM and 12 GB of user data.
- Where Free stops. Oracle does not restrict where Free is deployed, but it carries no support and receives no patches, security patches included. Its caps cannot be raised, so a production system that outgrows them has to move to a licensed edition. The 23ai licensing guide covers the detail.
Oracle Database Options and Packs Analysis
Every option and pack ordered by cost, with what triggers each one and how to remediate before an audit prices it at list.
Get the white paper →Which Oracle licensing documents are actually binding?
Only three of the eight documents that govern an Oracle Database purchase are contract: the ordering document, the master agreement and the support policies. The Core Factor Table is usually incorporated by reference. The rest are price list, documentation and policy, and Oracle can revise them without your signature.
| Document | What it decides | Contractual? |
|---|---|---|
| The ordering document | Programs, quantities, metric, territory, price | Yes, and the line that binds |
| The master agreement | Definitions, audit clause, assignment, termination | Yes |
| Support policies | Matching service levels, repricing when licenses are dropped | Yes, through the support renewal |
| The Core Factor Table | The multiplier on physical cores | Incorporated by reference in most orders |
| The Technology Global Price List | List price per program per metric | No, though every quote is built from it |
| The Licensing Information manual | Which feature needs which option or pack | No, it is documentation, and it is what the auditor reads |
| The Partitioning Policy | Which virtualization counts as hard partitioning | Policy only, rarely in an ordering document |
| The cloud policy | vCPU counting in authorized public clouds | Policy only |
Why do the two policy documents decide the largest numbers?
The partitioning policy governs cluster counting under virtualization, and the cloud policy governs the vCPU conversion. Neither is normally part of what you signed, and Oracle can and does revise both on its own.
That does not make them irrelevant. It turns the largest counting arguments from compliance questions into commercial ones, which is a conversation you can win. An auditor will quote all eight documents in the same tone, so your job is to know which ones you actually agreed to.
Should you license every host the partitioning policy points to?
The usual advice is to license every host in any VMware cluster where Oracle Database could run, because the partitioning policy says so. We think that treats a policy document as if it were contract. In most accounts the policy sits outside the ordering document, so the host count is open to negotiation.
The better course is to restrict the database to dedicated hosts, keep the placement and migration records that prove it, and argue the rest from what you signed.
Which pricing errors overstate an Oracle Database bill?
Most overstated bills come from a price applied to the wrong line. Three errors recur in the reviews we run. The first two inflate the number, and the third leaves real usage uncounted until an auditor finds it.
- The $23,000 rate on the wrong options. Teams quote $23,000 per processor across twelve line option stacks. Only three current lines carry it: Real Application Clusters, Database In-Memory and TimesTen Application-Tier Database Cache.
- Options that became free in 2019. Spatial and Graph and Advanced Analytics, now Oracle Machine Learning, stopped being separately licensed on December 5, 2019 for Enterprise Edition and SE2 customers on active support. Internal budgets still carry $17,500 and $23,000 per processor for them.
- The fifth pack. Most summaries list four packs: Diagnostics, Tuning, Database Lifecycle Management and Cloud Management. Data Masking and Subsetting, the fifth priced pack at $11,500 per processor, is missing from most internal inventories until an audit prices it. Our Data Masking pack analysis covers what triggers it.
What does a mispriced option stack cost in practice?
Say you run Enterprise Edition on 8 processors with Partitioning, Advanced Compression, Active Data Guard, Diagnostics and Tuning. Your budget quotes the three options at $23,000 and still carries Spatial and Graph.
| Line | Budgeted rate | Correct rate | Budgeted for 8 | Correct for 8 |
|---|---|---|---|---|
| Partitioning | $23,000 | $11,500 | $184,000 | $92,000 |
| Advanced Compression | $23,000 | $11,500 | $184,000 | $92,000 |
| Active Data Guard | $23,000 | $11,500 | $184,000 | $92,000 |
| Diagnostics and Tuning packs | $12,500 | $12,500 | $100,000 | $100,000 |
| Spatial and Graph | $17,500 | Included since 2019 | $140,000 | $0 |
| Total | $792,000 | $376,000 |
The budget is $416,000 too high at list, before any discount. At the support rate it also overstates the run cost by $91,520 a year, or $457,600 over five years. The database licensing calculator runs the same arithmetic on your own configuration in minutes.
How does support pricing compound each error?
Oracle support costs 22 percent of the original net license fee every year for as long as you renew. It is set by what you first paid and does not fall with this cycle's discount or a smaller footprint later. Over five years the support stream passes the license fee itself.
Dropping licenses does not cut support in proportion, because the matching service levels policy keeps a license set on one support level and terminating part of it reprices the rest. Reconcile both ways each year, for missing licenses and for shelfware. Our support renewal checklist lists the clauses involved.
How do you check which Oracle Database features you actually use?
Start from the databases and work back to the contract. Almost every priced option installs by default and runs without a license key, so the fact that a feature works proves nothing about entitlement. These sources show what is in use.
- V$VERSION. The edition and release of each instance.
- DBA_FEATURE_USAGE_STATISTICS. Which features have been used, with first and last usage dates.
- CONTROL_MANAGEMENT_PACK_ACCESS. On Enterprise Edition the default is DIAGNOSTIC+TUNING, so AWR reports, ADDM and the SQL Tuning Advisor work from day one with no license check, and their use is recorded. Set it to NONE where the packs are not licensed.
- Oracle's options and packs usage script. The options_packs_usage_statistics.sql script from My Oracle Support maps recorded usage to the option or pack that covers it.
- Hardware and placement records. Sockets and cores per host from lscpu or your inventory tool, plus cluster membership and VM placement history.
Our guide to Oracle license compliance scripts explains how to read the output before Oracle does.
Why read the Licensing Information manual for your own release?
Feature to edition mappings move between releases, and the auditor reads your version. Read the Licensing Information manual for the release you run, not the current one, before you concede any feature finding. The packs produce most of these findings, and our Diagnostics and Tuning pack guide shows which screens and views trigger them.
What will Oracle's account team say, and how should you reply?
The same few lines come up in most Oracle Database negotiations and audit closeouts, and each has a factual reply.
- "Every host in the cluster needs licensing under our partitioning policy." Ask where your ordering document or master agreement incorporates the policy. If neither does, discuss the host count commercially, starting from the hosts the database actually ran on.
- "Sign a larger order and we can close the audit findings." Ask for every finding priced line by line against the dated price list and your ordering documents first. Settle each one on its own merits before you discuss any new purchase.
- "Spatial is in use, so it is a finding." Spatial and Graph is included with Enterprise Edition and SE2 for customers on active support. Ask for it to be struck from the report.
- "Your AWS instances count at the core factor." The cloud policy replaces the core factor with a vCPU count. With multithreading enabled, a 16 vCPU instance needs 8 processor licenses.
- "Dropping these licenses will not reduce support much." Ask for the repricing calculation line by line, per license set, with the price list date used, and compare it with the support policy text.
Which contract terms should you ask for before you sign?
- A fixed policy version. The partitioning and cloud policies apply as of the order date, or not at all, so a later revision cannot change your count.
- Option price holds. The agreed discount on named options and packs holds for additional quantities over a stated period, since options carry most future spend.
- A cap on annual support increases. Written into the order, it limits how far the support fee can rise each year after signature.
- A narrow license set definition. Keep each order's programs in their own license set, so a later reduction reprices only that set and leaves the rest of your support alone.
- Audit remediation. A window to remove a feature or buy it at the contracted discount before list price applies to a finding.
What have we seen in Oracle Database reviews in 2024 and 2025?
Across roughly 40 to 55 Oracle Database and Java engagements I led in 2024 and 2025, the most common cause of an overstated bill was a price applied to the wrong line. A missing entitlement was the cause far less often.
The two errors we met most were the $23,000 rate spread across whole option stacks and budget lines for Spatial and Graph and Advanced Analytics years after they became free. None of them was Oracle's fault. Each was fixed by pricing the line against the dated documents.
Every wrong line price we found in those reviews ran in Oracle's favor.
What to do next
- Sort your document file. Separate the three binding documents from the policy and reference material.
- Reprice the option stack. Price every line against the dated technology price list, removing the lines free since 2019 and any wrong $23,000 rates.
- Test both metrics. Price each server on processors and on Named User Plus at the minimums, 25 per processor on Enterprise Edition and 10 per server on SE2, before accepting either.
- Check usage before conceding. Run the feature usage views and the usage script, then read the Licensing Information manual for your release.
- Reconcile support every year. Compare the support base with the catalog in both directions, compliance gaps and shelfware, because support compounds every error.
- Fix the terms at the next order. Put the policy version, price holds and support cap into the next ordering document. Our Oracle practice runs this reference with you.
Frequently asked questions
What does an Oracle Database license cost?
At list, Enterprise Edition costs $47,500 per processor or $950 per Named User Plus, and Standard Edition 2 costs $17,500 or $350. Options and packs come on top, from $5,000 for the Tuning Pack to $23,000 for RAC. Discounts are negotiated per deal, so the list is the starting point for every quote.
Where can I find the official Oracle Database price list?
Oracle publishes it as the Technology Global Price List, a PDF on oracle.com that it revises from time to time. The current edition is dated September 15, 2026. Save a copy on the day you sign each order, because the dated version is what your discount and support base were calculated from.
Which Oracle licensing documents are actually contractual?
Your ordering documents, the master agreement they reference, and the support policies that apply through each renewal. Anything else, including the partitioning and cloud policies, binds you only if an ordering document names it, so check the incorporation language in each order before an audit starts.
What is the difference between SE2 and Enterprise Edition licensing?
SE2 runs only on servers with at most two sockets, limits each database to 16 CPU threads and cannot take options or packs. Enterprise Edition has none of those limits. Enterprise Edition costs 2.7 times as much per unit, and because SE2 counts sockets while Enterprise Edition counts cores, the real gap on a dense modern server is far wider.
Are any old Oracle Database options now free?
Yes. Oracle Spatial and Graph and Oracle Advanced Analytics, renamed Oracle Machine Learning, have been included with Enterprise Edition and SE2 since December 5, 2019, for customers with active support. If your support contracts still list them as separate lines, ask Oracle how they are treated at your next renewal before you pay for another year.
How does Oracle Database support pricing work?
Annual support is 22 percent of the net license fee you originally paid, and Oracle usually raises it each year unless your order caps the increase. A reduction rarely lowers the bill in proportion, so ask Oracle for the repriced quote in writing before you give notice to drop any licenses.
Does a feature running mean it is licensed?
No. Oracle ships most options and packs inside the Enterprise Edition binary with no license key, so a feature that works may still be unlicensed. Check DBA_FEATURE_USAGE_STATISTICS, then confirm against the Licensing Information manual for your release. Disabling a feature after use does not erase the recorded usage history.