How to check your Oracle license position
There is no single Oracle license dashboard. The position is triangulated from three sources: the measurement scripts auditors use, Enterprise Manager usage data, and the entitlement records behind your CSI numbers. Each view lies in its own way, and the gap between them is your risk.
Prepared by Redress Compliance · August 6, 2026 · Oracle licensing advisory. Based on 30 to 40 license baselines built or reviewed 2024 to 2026.
Executive summary
Oracle entitlements live in contracts and the support portal. Deployments live on your servers.
Nothing reconciles the two for you, and the distance between them, unentitled options running in production, support renewing on shelfware, contracts nobody can find, is exactly what an Oracle audit monetizes.
Checking your license position means building that reconciliation yourself, from three sources that each cover a different part of the truth.
The measurement scripts, the same tooling Oracle's audit function runs, are read only and available to you.
Run internally, on your schedule, they give you the auditor's view without the auditor. Enterprise Manager shows feature usage across the estate.
And is itself a licensing trap: the Diagnostics and Tuning packs it surfaces are separately priced and easy to invoke by accident. My Oracle Support holds the CSI records: what you pay support on per contract, which is related to, and reliably different from, what you own.
The reconciliation is not optional polish. Across the license baselines we built or reviewed, no estate's three views agreed on the first pass.
The recurring gaps: Diagnostics, Tuning, or Partitioning enabled on 20 to 40 percent of databases without a matching entitlement, support renewing annually on licenses with no deployment behind them, and entitlement records scattered across acquisition era contracts nobody had consolidated.
The output that matters is a dated, owned baseline: deployments, entitlements, and the delta, signed by someone who will keep it current.
It is the only defensible license position, it is what turns an audit letter from a crisis into a correspondence, and it is the artifact every negotiation in the Oracle estate ultimately stands on.
Why there is no dashboard, and what that means
Oracle licensing is contractual, not technical. The software installs everything, enables most things, and enforces nothing: an Enterprise Edition binary will happily run Partitioning, Advanced Compression, and every management pack whether or not a single line of entitlement exists.
The license position is therefore a reconciliation between two datasets that live in different worlds, deployment facts on your servers and entitlement facts in your contracts, and Oracle offers no tool that joins them.
That design is not an oversight; it is the audit business model. Every check below exists because the burden of knowing sits entirely on the buyer, and the three sources cover different parts of it:
| Method | What it reads | Handle with care |
|---|---|---|
| The measurement scripts | Installs, options, packs, and hardware counts, read directly from each environment | Run them internally on your schedule. Never run Oracle supplied discovery for the first time during an audit. |
| Enterprise Manager | Feature usage and database inventory across the estate | The Diagnostics and Tuning packs it exposes are licensable. Set pack access controls before anyone explores. |
| My Oracle Support, the CSI records | Supported quantities, metrics, and end dates per contract | A lead, not a verdict: it carries shelfware and omits perpetual licenses whose support you dropped. |
Method one, the measurement scripts
Oracle's license management function, GLAS, formerly LMS, measures estates with a documented script set, and the database side centers on options_packs_usage_statistics.sql: a read only query pass that reports option usage, management pack usage, and feature invocation per database.
The scripts are available to customers, and running them internally is the single highest value habit in Oracle license management, because it shows you precisely what an audit would find, before an audit finds it.
The output needs interpretation, and the sampling semantics are where self assessments go wrong:
- CURRENTLY_USED reads one weekly sample. The flag reflects only the most recent collection, so a feature that runs monthly can show false on the day you look.
- The history is the finding. A priced option invoked once, two years ago, still sits in the usage history, and Oracle's position is that invocation is use. Clearing the deployment does not clear the record.
- Accidental enablement counts. Restoring from a compressed backup, running a default installer, or a DBA exploring a menu can light up an option. Intent is not a licensing defense; the reconciliation is.
The full interpretation guide, script by script and column by column, is in the compliance scripts guide, and the script analysis covers what the wider GLAS collection set gathers beyond the database.
The same discipline is the backbone of Java audit defense, where the inventory question arrives by letter.
The Oracle measurement scripts, decoded
What every script collects, how GLAS reads the output, the false positive patterns, and the internal run book for building the auditor's view on your own schedule.
Get the white paper →Method two, Enterprise Manager, the view that bills you back
Enterprise Manager gives the estate wide view the scripts give per database: feature usage, database inventory, and trend data across everything it monitors. It is the fastest way to see the whole picture, and it is the one method that can create the liability it is measuring.
The mechanism is the management packs. The Diagnostics and Tuning packs are separately priced products, licensed per processor or named user on the target database and requiring Enterprise Edition underneath, and Enterprise Manager surfaces their screens by default.
A DBA who clicks into a performance page has invoked the pack, and the invocation lands in the same usage history the scripts read.
In our baselines, unentitled Diagnostics, Tuning, or Partitioning usage appeared on 20 to 40 percent of databases, and Enterprise Manager exploration was a leading cause.
Set pack access controls before anyone explores. Enterprise Manager has a per target setting that disables pack access outright. Configuring it first, and documenting the date you did, is the difference between a usage history you can explain and one you settle.
The management pack licensing guide covers the pack by pack pricing and rules.
Method three, the CSI records in My Oracle Support
The support portal organizes your relationship with Oracle by Customer Support Identifier, and each CSI carries the supported products, license metrics, quantities, and end dates from its originating contract.
It is the closest thing to an entitlement inventory Oracle offers, and it must be read as a lead rather than a verdict, because it diverges from ownership in both directions:
- It overstates through shelfware. CSI lines renew annually whether or not a deployment exists behind them. Support paid on licenses nobody runs is pure recoverable spend, and it hides inside every long standing CSI.
- It understates through dropped support. Perpetual licenses whose support lapsed disappear from the portal but remain owned. Estates that equate the portal with ownership under count their own entitlements.
- It fragments through history. Acquisitions, resellers, and decades of amendments scatter entitlements across CSIs and legal entities. In our baselines, no one could state what the company owned until the contracts themselves were consolidated.
The correction is documentary: pull the ordering documents behind every CSI, consolidate them into one entitlement register, and reconcile the register against the support renewal before paying it.
The Oracle SAM guide covers the register structure, and the audit secrets guide shows how Oracle uses the same fragmentation against unprepared estates.
- 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 license baselines, 2024 to 2026
Across roughly 30 to 40 Oracle license baselines Fredrik Filipsson built or reviewed between 2024 and 2026, the finding was identical on every engagement: no estate's three views agreed on the first pass. The recurring gaps:
Diagnostics, Tuning, or Partitioning enabled without a matching entitlement, mostly through defaults and exploration rather than intent.
Scripts, Enterprise Manager, and the CSI records told three different stories on every estate until deliberately reconciled.
The quieter findings cost as much as the loud ones: support renewing on shelfware year after year, and measurement owned by nobody, the scripts run once by a contractor whose output could not be found. A baseline that is not owned and dated decays into exactly the ambiguity an audit letter exploits.
Building the baseline, your first five moves
- Run the measurement scripts internally, on every environment, on a schedule you own. Keep the raw output; it is your evidence either way.
- Lock Enterprise Manager pack access first, then use its estate wide usage views. Document the date the controls went on.
- Consolidate the entitlement register from the ordering documents behind every CSI, including acquisition era contracts and lapsed support perpetuals.
- Reconcile the three views into one dated baseline: deployments, entitlements, delta, and an owner. Re run it before every support renewal and every true up.
- Act on the delta from your side. Remove or entitle unlicensed usage, cut support on verified shelfware, and hold the baseline current so an audit meets a document instead of a scramble. The Oracle practice and Vendor Shield keep it standing between renewals.
Frequently asked questions
Is there a dashboard that shows my Oracle licenses?
No. Oracle provides no tool that joins entitlements to deployments. Entitlements live in contracts and the CSI records in My Oracle Support; deployments live on your servers and are read by the measurement scripts and Enterprise Manager.
The license position is a reconciliation you build, and in our baselines the views never agreed on the first pass.
Can I run Oracle's audit scripts myself?
Yes. The measurement scripts, including options_packs_usage_statistics.sql on the database side, are read only and available to customers. Running them internally on your own schedule shows you exactly what a GLAS audit would find.
What you should not do is run Oracle supplied discovery for the first time during a live audit, on Oracle's schedule.
Why does a feature we never use show as used?
The feature usage views record invocation history, and Oracle's position is that invocation is use. A default installer, a restore from a compressed backup, or a DBA opening a Diagnostics page can light up a priced option, and the record persists after the deployment is cleaned.
CURRENTLY_USED reflects only the latest weekly sample, so the history, not the flag, is what an audit reads.
Does Enterprise Manager require extra licenses?
The console itself ships with the database, but the Diagnostics and Tuning packs it surfaces are separately priced, licensed per processor or named user on the target, and easy to invoke by accident because their screens are exposed by default.
Set the per target pack access controls before anyone explores, and document when you did.
Is what My Oracle Support shows the same as what we own?
No. The CSI records show what you pay support on, which overstates ownership through shelfware lines renewing with no deployment behind them, and understates it by omitting perpetual licenses whose support you dropped.
The ordering documents behind each CSI, consolidated into one register, are the entitlement truth.
How often should the license baseline be refreshed?
Before every support renewal, every true up, and any audit response, with a named owner and a date on each version.
Estates that built a baseline once and stopped decayed back into ambiguity, and the scripts run by a departed contractor whose output nobody could find were a recurring finding in our engagement file.
