How to view Oracle license information. Your contracts against what you run.

Oracle has no screen that shows your license position. You view it by matching the entitlement in your ordering documents and master agreement against what your servers actually run, and the difference is what an audit would bill.

Where can you view your Oracle license information?

You view it in two places and join them yourself. What you are entitled to use sits in your signed paperwork: the ordering documents, the master agreement and the support renewal record. What you actually run sits on your servers. No Oracle portal shows a clean, complete and legally reliable entitlement position.

Most confusion comes from treating a partial source as the whole answer. My Oracle Support shows support identifiers and patch access, and a discovery report shows what is installed. Neither tells you whether a deployment is licensed. The table sets out what each source can and cannot prove.

How do the entitlement documents rank?

Three documents define what you own, in strict order. The ordering document states products, quantities, metrics and any special terms. The master agreement (an OMA, OLSA or older equivalent, see our note on agreement structures) states the rights, the audit clause and the restrictions. The support renewal record shows what is still supported.

The policy documents Oracle publishes, such as the price list, the partitioning policy and the cloud policy, describe how Oracle reads the grant. The grant itself is your own signed paper. Where acquisitions sit behind the contracts, reconstructing that paper often takes longer than the counting.

• Ordering documents. Every one since the first purchase, including those signed by companies you acquired. Perpetual licenses stay valid after support lapses, so old orders still matter.
• Master agreements. The version each order references, because definitions and audit terms changed over the years.
• Support renewal quotes. Map every Customer Support Identifier (CSI) line back to the order that created it.
• ULA certification letters. If you ever exited an unlimited agreement, the certified quantities are your entitlement for those products.
• Migration and transfer paperwork. Metric conversions and license migrations change what a line means.

How does Oracle count what you deploy?

Oracle counts four things per product, in a fixed order. First the hosts: every physical server and virtual machine where the software is installed, live or otherwise. Then cores and sockets with the processor model, because the model sets the core factor. Then users and devices, human and non human, and finally options and packs per database.

Label every host with its environment type and business owner as you go. Unlabeled hosts default to production pricing in any audit position paper. Test environments need licenses like production, and recovery copies follow separate rules, so read Oracle's data recovery licensing document before assuming a standby is free.

How does the core factor change the processor count?

For Enterprise Edition, you total the cores the program runs on, multiply by the factor for that processor model and round any fraction up. Current Intel Xeon and AMD EPYC chips carry a factor of 0.5, and IBM POWER6 through POWER10 carry 1.0. Oracle's own worked example shows the direction: 6 cores at 0.25 equals 1.5, which becomes 2 licenses.

Standard Edition 2 ignores the core factor. It counts occupied sockets, and it may only be licensed on servers with a maximum capacity of 2 sockets. File a dated copy of the factor table with each count, since Oracle revises it as new chips ship.

Why do Named User Plus minimums catch buyers out?

Named User Plus carries a floor that most buyers miss. Enterprise Edition requires 25 Named User Plus per processor or the actual count if higher, and Standard Edition 2 requires 10 per server. A small user base on a large server is priced by the hardware whatever your headcount says.

The definition also covers machines. Oracle counts a non human operated device that can access the programs as a Named User Plus, on top of every authorized person. Batch interfaces, monitoring agents and IoT feeds therefore break NUP counts that listed only people. Our notes on devices and batch users and the minimum worked examples go further.

What changes on VMware and in public cloud?

The counting rules shift at two boundaries. On virtualization, Oracle's partitioning policy does not accept soft partitioning as a way to limit licenses, and its position expands the count to every host in the cluster. A small database VM can pull a whole VMware cluster into scope.

In the cloud, the core factor stops applying. On AWS, Azure and Google Cloud, Oracle counts two vCPUs as one processor license when multithreading is enabled. Eight Intel cores on premises need 4 licenses. The same 8 cores exposed as 16 vCPUs need 8, so a workload can cost more per core than on your own hardware.

How do you check your own counts?

• Feature usage. Run options_packs_usage_statistics.sql from MOS Doc ID 1317265.1, which reads DBA_FEATURE_USAGE_STATISTICS. Keep the dated output per host. Our notes on first and last sample dates explain the columns.
• Pack access. Check the CONTROL_MANAGEMENT_PACK_ACCESS parameter. It defaults to DIAGNOSTIC+TUNING on Enterprise Edition, so set it to NONE wherever you hold no pack licenses.
• Processors. On Linux, lscpu gives sockets, cores per socket and the CPU model name. Record the model, because the factor depends on it.
• Cluster scope. Export host membership for every vSphere cluster that runs an Oracle VM, and keep a record of every VM migration between clusters.
• Users. Pull database accounts from DBA_USERS, then trace application pools and interfaces back to the people and devices behind them.

The full script by script guide is in our compliance scripts guide, and the Diagnostics and Tuning Pack guide covers the two packs flagged most often.

What does a reconciliation look like in numbers?

A worked example shows how the gaps add up. Say you run Oracle Database Enterprise Edition on three Intel Xeon hosts. Price any shortfall at the technology price list: $47,500 per processor, $950 per Named User Plus, and $7,500 per processor for the Diagnostics Pack. All figures are hypothetical and at list.

Host 2 has only 60 users and devices, yet the minimum sets the requirement at 100. Host 3 carries about three quarters of the exposure through cluster scope, a design problem you can fix before buying anything. Counting Host 1's 32 cores without the factor would have reported an 18 processor shortfall that does not exist.

The reconciliation also runs the other way. Suppose the same company still holds 4 Enterprise Edition processor licenses from a retired reporting server. That is $190,000 of licenses at list paying about $41,800 a year in support for nothing. The database licensing calculator runs this counting arithmetic in minutes for your own hosts.

What have we seen in Oracle license reconciliations from 2022 to 2025?

Across roughly 40 to 60 Oracle environments I reconciled between 2022 and 2025, the gap was almost never where the client expected it. Teams watched headcount and total cores, while the errors sat in how the core factor was applied, in the user minimums and in cluster scope.

• Processors over counted by 20 to 40 percent. Before the core factor was applied per processor model and rounded correctly, internal counts regularly overstated what was owed.
• About 1 in 3 gaps came from NUP minimums. The 25 per processor floor and non human devices drove them, never the headcount everyone monitored.
• Virtualization doubled the count or worse. Where VMware clusters were not contained, the core count Oracle would claim rose by a factor of 2 or more.
• Shelfware deserved equal attention. Entitlement above deployment paid 22 percent support every year, and it could only be recovered if the reconciliation found it before the renewal signed.

A gap you find on your own calendar is a purchasing decision. The same gap found by an auditor is a settlement priced on Oracle's terms.

Why we would not start with a discovery tool

A common recommendation is to buy a software asset management tool, run discovery everywhere and read the compliance dashboard. We think that order is backwards. Discovery answers only the deployment half, and the dashboard compares it with whatever entitlement someone typed in, usually from support quotes, which drop unsupported perpetual licenses.

Rebuild the entitlement archive first, then point the tool at a known list of products and metrics. Our comparison of tooling options covers where each approach fits.

How should you treat Oracle feature usage findings?

Treat a feature usage flag as a lead to investigate before you concede anything. The dictionary counters are blunt. A single console click, a default maintenance job or a health check can register usage of a separately licensed pack, and the record stays after the cause is gone.

For every flagged option or pack, establish who invoked it, when, and whether any workload ever depended on it. A counter incremented once in 2019 is not a business use of the Tuning Pack. Read the counters quarterly so the explanation is written while the people involved still remember it.

What will Oracle say, and how should you answer?

Expect a handful of standard lines once Oracle's account team or audit function sees your data. Each has a factual answer worth preparing in advance.

1. "Your support records show what you own." Reply that support records show what is supported. Send the list of ordering documents, including perpetual licenses whose support you dropped.
2. "The whole cluster needs licensing." Ask Oracle to show where your signed agreement incorporates the partitioning policy, and bring your cluster membership and VM placement records.
3. "Feature usage shows the Tuning Pack in use." Ask for the detection count and the first and last usage dates, then answer with your written explanation of each record.
4. "Unlabeled servers are production." Provide your environment register with an owner against every host.
5. "Please run our scripts on every server this week." Point to the audit clause. Oracle's standard terms give 45 days written notice, so run the scripts internally first and agree scope in writing.

If a formal letter arrives anyway, our audit secrets guide covers the response.

When should you run an Oracle license reconciliation?

Run it once a year and again before every support renewal. The renewal date sets the schedule, because unused licenses come off support only at renewal and any shortfall is best bought in the same negotiation. Work back from that date.

How do you recover shelfware without raising your support bill?

Model the renewal before you cancel anything. Under Oracle's Technical Support Policies, dropping licenses from an order reprices support on the licenses left on that order at current list less the standard discount, capped at what you paid before. The saving can therefore be smaller than the line you cut.

Our guide to identifying and reclaiming shelfware covers the options in more detail.

Which mistakes cost the most?

• Reading CSI lines as ownership. Unsupported perpetual licenses disappear from the count and shelfware looks used.
• Counting only people. Devices and interfaces push NUP past the entitlement, then the minimum raises it further.
• Carrying on premises assumptions into cloud. The core factor does not apply there, and Standard Edition 2 is capped at 8 vCPUs per instance.
• Leaving Oracle VMs unpinned. Each new cluster an Oracle VM can reach adds its hosts to Oracle's count.

What to do next

1. Reconstruct the entitlement archive. Collect ordering documents, master agreements and support records, because no console will do it for you.
2. Run the four counts per product. Count hosts, cores with processor models, users with devices, and options, with an environment and owner label on every host.
3. Apply the core factor and test the minimums. Round every fraction up, then check each NUP count against its floor.
4. Contain virtualization before it multiplies the count. Pin Oracle VMs to dedicated hosts, and recount from scratch for any cloud move.
5. Explain every feature flag in writing. Record who, when and why, and switch off pack access you do not license.
6. Reconcile annually and before every renewal. Work in both directions, buying shortfalls and retiring shelfware on your own schedule. Our Oracle practice can run the reconciliation with you.

Frequently asked questions