Oracle license info. Entitlement versus use.

Checking Oracle license information means reconciling your contracted entitlements against what you actually deploy. The ordering documents are the entitlement, the deployment is the usage, and any gap between them is what an audit will bill.

This guide is for Oracle estate owners and procurement teams in 2026. Read it with the three ways to check Oracle license information and the Oracle Practice page so entitlement and deployment stay aligned.

Where do you find your Oracle entitlements?

Entitlements are recorded in your signed paperwork, not in a console. The ordering document and license agreement state what you bought and the metric. Your Oracle account record confirms it.

Which documents define what you own?

The ordering document lists products, quantities, and metrics. The master agreement sets the use rights. Oracle publishes its current price list and policies on its pricing pages.

• Ordering document: products, quantities, and metrics purchased.
• License agreement: the rights and restrictions on use.
• Account records: confirmation of holdings and support.

How do you measure deployment?

Deployment is what runs in your environment. Inventory installations, count the relevant metric for each, and capture virtualization details. This is the usage you reconcile against entitlement.

How do you reconcile entitlement against usage?

Lay the deployment count beside the entitlement for each product and metric. Where deployment exceeds entitlement, you have a gap. Where it falls short, you may hold shelfware.

Which metrics need the most care?

Processor licensing carries the core factor, so the hardware matters. Named user plus has minimum counts per processor. Application metrics each have their own rules. Verify each one.

• Processor: cores times the published core factor.
• Named user plus: watch the per processor minimums.
• Application units: read the specific counting rule.

Oracle compliance is a reconciliation, not a report. The console tells you what is installed. Only the contract tells you what you are allowed to install. The gap between them is the whole game.

Why does virtualization need extra care?

Oracle's stance on soft partitioning can count cores beyond the virtual machine running the software. Document your controls so the processor count you defend is the one that actually applies.

What does an Oracle audit actually measure?

An Oracle audit measures deployment against entitlement, then prices the gap at list. The auditor counts what runs, applies the metric rules, and compares the result to your ordering documents. Your job is to reach that number first.

How does Oracle run the measurement?

Oracle's License Management Services team uses scripts and a review of your environment. Oracle sets the counting rules in its partitioning policy, its processor core factor table, and the software investment guide.

• Scripts: collected usage from each Oracle host.
• Metric rules: the policy that converts usage to licenses.
• Comparison: measured usage set against your entitlement.

What protects the buyer side count?

Your contract and the published core factor protect it. A discovery script reports installs, but the contract sets what Oracle may bill. Document your virtualization controls so the cores you defend are the cores that actually apply.

Where the common advice on Oracle license info is wrong

The standard advice is to trust an Oracle discovery script as the system of record for what you owe. We disagree. Across the Oracle estates Fredrik Filipsson reconciled between 2022 and 2025, the script regularly counted cores Oracle's own contract did not entitle it to bill, especially under virtualization and on cloud hosts. In more than half of those reviews the defensible number landed 20 to 40 percent below the script output. The buyer side move is to rebuild the count from your contract and the published core factor, then make Oracle defend any line that exceeds it.

20 to 40%

Typical gap between script and contract

1 in 3

Gaps driven by user minimums

2x

Core inflation from loose virtualization

Source: Redress Compliance advisory engagement file, 2024 to 2025.

What to do next

1. Gather every Oracle ordering document and master agreement.
2. Build an inventory of installed Oracle products and versions.
3. Count the correct metric for each deployed product.
4. Apply the processor core factor to processor based licenses.
5. Reconcile deployment against entitlement, product by product.
6. Document virtualization controls for every relevant environment.
7. Close any gap on your terms before a renewal or audit.

Frequently asked questions

How do you check your Oracle license entitlements?

Start with your Oracle ordering documents and the Oracle Store or My Oracle Support account, which list what you have purchased. Then reconcile that against deployment data. The contract is the entitlement, and the deployment is the usage you must match to it.

Where are Oracle entitlements actually recorded?

Entitlements live in your ordering documents, the related license agreement, and your Oracle account records. Tools report deployment, but the legal entitlement is the signed paperwork. Always reconcile reports against the contract, not the other way round.

What is the difference between entitlement and deployment?

Entitlement is what you are licensed to use under contract. Deployment is what you have actually installed and run. A compliance gap is any deployment that exceeds the matching entitlement, and that gap is what an audit bills.

Which Oracle metrics do you need to verify?

The common metrics are processor, named user plus, and various application specific units. Each has its own counting rules, and the processor core factor applies to processor licenses. Verify the metric and the count for every product you run.

How does the processor core factor affect Oracle licensing?

Processor licensing multiplies physical cores by Oracle's published core factor for your chip. Two servers with the same core count can require different license quantities. Always confirm the factor for your specific processors.

How do you stay compliant with Oracle licensing?

Keep a current reconciliation of entitlement against deployment, document virtualization controls, and review before any renewal or audit. Closing gaps on your own terms is far cheaper than settling them under audit pressure.

Can you check Oracle license info without a tool?

Yes. The authoritative check is documentary, not technical. Read your ordering documents for entitlement, inventory your installs for deployment, and apply the published metric rules. A tool speeds the count, but the contract defines what you owe.

How often should you reconcile Oracle licenses?

Reconcile at least once a year and before every renewal or audit. An annual cycle catches drift from new deployments early, while a pre renewal check gives you time to close any gap on your own terms rather than under pressure.