The Oracle license position, paperwork against deployment
Checking Oracle license information means reconciling what your contracts entitle you to against what your estate actually runs: the ordering documents are the entitlement, the deployment is the usage, and the gap between them is what an audit bills. Almost every tool in this space answers the second question and quietly implies it has answered the first. It has not.
Prepared by Redress Compliance · August 7, 2026 · Oracle advisory. Based on 40 to 60 Oracle estates reconciled 2022 to 2025.
Executive summary
Entitlement lives in paperwork, and nowhere else.
The ordering document states products, quantities, metrics, and special terms; the master agreement states the rights, the audit clause, and the restrictions.
The support renewal record evidences what is still supported. No Oracle portal shows a clean, complete, legally reliable entitlement position: My Oracle Support proves support and patch access, never use rights, and a discovery report proves what is installed, never whether it is licensed.
The counting rules run against you at every fraction. Processor counts across our reconciliations ran 20 to 40 percent high before the core factor was applied correctly, and Oracle's own worked example shows the direction: fractions always round up.
Named User Plus carries the floor most buyers miss, 25 per processor on Enterprise Edition or the actual count if higher, 10 per server on SE2, and the definition includes non human devices, which is why batch interfaces and IoT feeds break NUP counts, and why the minimums, not headcount.
Drove about one gap in three.
Virtualization and feature flags are the two silent multipliers.
Uncontrolled virtualization inflated the defensible core count by a factor of two or more, and the dictionary usage counters are blunt: a single console click, a default maintenance job, or a health check registers usage of a separately licensed pack.
Before accepting any options finding, establish who invoked the feature, when, and whether the workload ever depended on it, because a counter incremented once in 2019 is not a business use of the Tuning Pack.
The timing decides whether the gap is a purchase or a settlement. Reconcile annually and before every renewal: a gap found in your own time is a purchasing decision made on your terms and calendar, and the same gap found in an audit is a settlement priced on Oracle's.
The reconciliation resolves both directions, since entitlement above deployment is shelfware still paying 22 percent support.
The sources of truth, and what each actually proves
| Source | Proves | Does not prove |
|---|---|---|
| The ordering document | Products, quantities, metric, special terms | What is currently deployed |
| The master agreement | Use rights, the audit clause, restrictions | The quantities you hold |
| The support renewal quote | What is under support today | Full entitlement, including unsupported perpetuals |
| My Oracle Support | Support identifiers and patch access | Legal use rights or metric definitions |
| A discovery tool report | What is installed and running | Whether any of it is licensed |
| A ULA certification letter | Quantities fixed at the certification date | Rights to deploy beyond that number afterward |
Three documents, in strict hierarchy, and everything else is commentary. The ordering document, the master agreement, and the support renewal record define what you own, and reconstructing that set is the first job of any license position: on older estates it takes longer than the counting.
The framework documents Oracle publishes surround the grant; the grant itself is your own signed paper.
The four counts, in the order Oracle counts them
Per product: hosts, every physical server and virtual machine where the software is installed, live or otherwise; cores and sockets with the processor model, because the model sets the core factor; users and devices, human and non human, because the NUP definition covers both.
And options and packs per database, with genuine use separated from counter noise.
Then two labels per host, environment type and business owner, because unlabeled hosts default to production pricing in any audit position paper.
The counting rules shift at two boundaries: virtualization, where the soft partitioning position expands the count to the cluster, and the cloud, where the core factor stops applying and vCPU counting can make the same workload more expensive per core than on your own hardware.
The Oracle CIO complete playbook
The five year plan the reconciliation anchors: the entitlement archive, the counting disciplines, the audit calendar, and the renewal sequence.
Get the white paper →The reconciliation, resolved in both directions
| Check | Source | The buyer action |
|---|---|---|
| Entitlement | The ordering documents | Confirm product, quantity, and metric |
| Deployment | The installed environment | Count the relevant metric per host |
| The core factor | Oracle's factor table, dated copy filed | Apply per processor model, then round up |
| User minimums | The product licensing rules | Test 25 per processor on EE, 10 per server on SE2 |
| Environment | Your own records | Label production, test, development, recovery |
| The gap | Deployment minus entitlement | Close it on your own terms and timeline, both directions |
- 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 reconciliations, 2022 to 2025
Across roughly 40 to 60 Oracle estates Fredrik Filipsson reconciled between 2022 and 2025, the gap was almost never where the client expected it:
Before the core factor was applied per processor model and rounded correctly.
Driven by the 25 per processor floor and non human devices, never by the headcount everyone watched.
The over licensing direction deserves equal attention: entitlement above deployment is shelfware paying 22 percent support forever, recoverable at the renewal wherever the reconciliation surfaces it first.
The feature usage discipline completes the position, dictionary counters read quarterly with the who, when, and whether it mattered established before any finding is conceded, and the whole exercise priced against the technology price list.
The database licensing calculator runs the counting arithmetic in minutes, and the audit secrets guide covers the posture when the letter arrives anyway.
Your first five moves
- Reconstruct the entitlement archive first: ordering documents, master agreements, and support records, because no console will do it for you.
- Run the four counts per product, hosts, cores with models, users with devices, and options, with environment labels on every host.
- Apply the core factor per processor model and round up, then test the NUP minimums, where a third of the gaps hid.
- Fix the virtualization boundaries before they double the count, and never carry on premises assumptions into cloud counting.
- Reconcile annually and before every renewal, in both directions, so gaps stay purchasing decisions. The Oracle practice runs the position with you.
Frequently asked questions
How do you check your Oracle license position?
By reconciling entitlement against deployment: the ordering documents and master agreement define what you own, the estate count defines what runs, and the gap between them is what an audit would bill.
No Oracle portal provides a reliable entitlement view, and discovery tools answer only the deployment half while implying they answered both.
Where do Oracle entitlements actually live?
In three documents in strict hierarchy: the ordering document for products, quantities, and metrics; the master agreement for use rights, the audit clause, and restrictions; and the support renewal record for what remains supported.
My Oracle Support proves patch access, not use rights, and reconstructing the archive is the first job of any position.
What are the most common Oracle counting errors?
Processor counts 20 to 40 percent high before the core factor was applied per processor model and rounded up; Named User Plus minimums missed, the 25 per processor EE floor with non human devices included, driving a third of the gaps.
And uncontrolled virtualization inflating the defensible core count by two times or more under the cluster position.
Do batch jobs and devices count as Oracle users?
Yes: Oracle's Named User Plus definition covers non human operated devices accessing the database, so batch interfaces, monitoring agents, and IoT feeds count toward the NUP total alongside people, subject to the per processor minimums.
This is why NUP counts break in estates that only ever counted the humans.
Is Oracle feature usage data proof of a compliance gap?
Not by itself: dictionary counters increment on default maintenance jobs, health checks, and single console clicks, so a flag is evidence to investigate, not a finding to concede.
Establish who invoked the feature, when, and whether any workload depended on it, because one exploratory click years ago is not business use of a pack.
How often should an Oracle license reconciliation run?
Annually, and before every renewal: a gap found in your own time is a purchasing decision on your terms, the same gap found in an audit is a settlement on Oracle's, and the shelfware direction, entitlement above deployment still paying 22 percent support.
Only recovers when the reconciliation finds it before the renewal signs.
