Oracle Database licensing, the numbers and the documents that bind
This is the lookup layer for Oracle Database licensing: the editions, the options and packs, both metrics with their minimums, and the counting rule per platform, with the list numbers attached. Two thirds of the spend on a typical estate sits in options and packs, not the base edition, and the most common overstated bill was not a missing entitlement; it was a price applied to the wrong line.
Prepared by Redress Compliance · August 7, 2026 · Oracle advisory. Based on 40 to 55 Oracle Database and Java engagements led 2024 to 2025.
Executive summary
One ratio settles the metric question. Every Database line prices Named User Plus at exactly one fiftieth of Processor: $47,500 and $950 on Enterprise Edition, $17,500 and $350 on Standard Edition 2, options included.
The minimums frame the crossover, 25 NUP per processor on EE and 10 per server on SE2, and SE2 counts an occupied socket as one license rather than cores times a factor, the single largest structural difference between the editions.
The catalog errors all run in Oracle's favor.
Teams quoted $23,000 per processor across twelve line option stacks when only three lines carry that number; Spatial and Graph and Advanced Analytics stopped being separately licensed in 2019 and estates still budget $17,500 and $23,000 for them.
And the fifth priced pack, Data Masking and Subsetting at $23,000, sits outside the four pack summaries and most internal inventories.
Price every line against the dated price list yourself.
Only three of the eight governing documents are contract.
The ordering document, the master agreement, and the support policies bind.
The price list, the licensing manual, and critically the partitioning policy and the cloud policy are not in most ordering documents, which converts the largest counting arguments from compliance questions into commercial ones, a conversation you can win.
And the core factor table does not apply in AWS or Azure, where the rule is two vCPUs to one license with hyperthreading, whatever chip is underneath.
Support is 22 percent of the original net fee, forever. Not of what you paid this cycle, and not of a reduced footprint later: across five years the support stream exceeds the license fee, which is why the shelfware direction of every reconciliation matters as much as the compliance direction.
The software letting you run something is not permission, almost every priced option installs by default and runs without a key, and the licensing manual for your release, not the binary, defines the entitlement.
The document stack, and what each one binds
| Document | What it decides | Contractual? |
|---|---|---|
| The ordering document | Programs, quantities, metric, territory, price | Yes: the line that binds |
| The master agreement | Definitions, audit clause, assignment, termination | Yes |
| Support policies | Matching service levels, repricing on dropped licenses | Yes, via 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, but every quote builds off it |
| The Licensing Information manual | Which feature needs which option or pack | No: documentation, and 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 AWS and Azure | Policy only |
The two policy documents decide the largest numbers. The partitioning policy and the cloud policy govern the cluster counting and the vCPU conversion, neither is normally part of what you signed, and Oracle can and does revise both unilaterally.
That does not make them irrelevant; it changes the conversation from compliance to commercial, and an auditor will quote all eight documents in the same tone of voice. Your job is knowing which ones you actually signed up to.
The edition matrix, and the two nobody summarizes
| Capability | Standard Edition 2 | Enterprise Edition |
|---|---|---|
| Maximum sockets | 2 per server, 16 thread cap | 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 |
| The minimum | 10 NUP per server | 25 NUP per Processor |
| The counting rule | One occupied socket = one license | Cores times the core factor, rounded up |
The database options and packs analysis
The full catalog ordered by what it costs: the trigger states, the five priced packs, the free lanes, and the remediation paths that avoid list price findings.
Get the white paper →The lookup discipline, before any argument
Two rules of thumb from using the Licensing Information manual in anger: the software letting you run something is not permission, because almost every priced option installs by default and runs without a key, and you read the manual for the release you run.
Not the current one, because feature to edition mappings move between releases and the auditor reads your version.
The two editions nobody puts in the summary carry their own surprises: Personal Edition licenses per NUP with the full EE feature set including options, which is why it surfaces as an audit finding on developer laptops, and Oracle Database Free, the renamed Express Edition.
Carries resource caps and no right to become a production dependency you then extend, the detail in the 23ai licensing guide.
The counting rules per platform complete the reference: the core factor on premises, the partitioning positions under virtualization, and the vCPU rules in the cloud, priced line by line against the technology price list.
- 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
What we saw across the 2024 and 2025 file
Across roughly 40 to 55 Oracle Database and Java engagements Fredrik Filipsson led in 2024 and 2025, the single most common cause of an overstated bill was not a missing entitlement; it was a price applied to the wrong line:
The $23,000 rate quoted across option stacks where only three lines carry it, and budgets for options free since 2019.
None of them Oracle's fault, and all of them correctable by pricing against the dated documents yourself.
The support line frames the stakes: 22 percent of the original net license fee, annually, exceeding the license cost across five years and repricing under the matching service levels policy when licenses drop, which makes every catalog error a compounding one.
The deep dives sit one layer down, the Diagnostics and Tuning pack guide and the Data Masking pack analysis for the packs that dominate findings, and the database licensing calculator runs the whole arithmetic in minutes.
Your first five moves
- Separate the contract from the policy in your document file, because only three of the eight bind and the auditor quotes all eight alike.
- Reprice the option stack line by line against the dated price list, removing the free since 2019 lines and the wrong rate quotes.
- Test both metrics with the one fiftieth ratio and the minimums, 25 per processor EE and 10 per server SE2, before accepting either.
- Read the licensing manual for your release before conceding any feature finding, because the binary is not the entitlement.
- Reconcile the support base against the catalog annually, both directions, because 22 percent forever compounds every error. The Oracle practice runs the reference with you.
Frequently asked questions
What does an Oracle Database license cost?
Enterprise Edition lists at $47,500 per Processor or $950 per Named User Plus; Standard Edition 2 at $17,500 and $350, with every Database line pricing NUP at exactly one fiftieth of Processor, options included.
Two thirds of a typical estate's spend sits in the options and packs on top, which is why the catalog prices line by line, never by summary.
Which Oracle licensing documents are actually contractual?
Three of the eight: the ordering document, the master agreement, and the support policies incorporated into the renewal.
The Core Factor Table is usually incorporated by reference, while the price list, the Licensing Information manual, the partitioning policy, and the cloud policy are documentation and policy, revisable unilaterally, and the largest counting arguments turn on exactly that distinction.
What is the difference between SE2 and Enterprise Edition licensing?
SE2 caps at two sockets per server with a sixteen thread limit and no options, counting one occupied socket as one Processor license with a 10 NUP per server minimum; EE counts cores times the core factor rounded up, carries the full option catalog, and requires 25 NUP per processor.
The unit price ratio is 2.7 times on either metric.
Are any old Oracle Database options now free?
Yes, two that estates still budget for: Spatial and Graph and Advanced Analytics stopped being separately licensed in 2019, and internal inventories still carrying $17,500 and $23,000 per processor for them overstate the estate.
The fifth priced pack, Data Masking and Subsetting at $23,000, cuts the other way, sitting outside most four pack summaries.
How does Oracle Database support pricing work?
At 22 percent of the original net license fee annually, not of the current footprint: dropping licenses triggers repricing under the matching service levels policy, and across five years the support stream exceeds the license fee.
Every catalog error therefore compounds, which is why the annual reconciliation runs in both directions, compliance and shelfware alike.
Does a feature running mean it is licensed?
No: almost every priced option installs by default and runs without a key, so the binary proves nothing about entitlement.
The Licensing Information manual for your release, not the current one, defines which feature requires which option or pack, and reading it before conceding any finding is the cheapest defense in the catalog.
