How to check Oracle license information the three reliable options.

There are three reliable ways to read what Oracle thinks you own, and each one shows a different slice of the truth. Knowing which to trust protects you in an audit.

This guide is for license managers, IT asset managers, and procurement leads who need a defensible view of their Oracle position before a renewal or an audit. Read it with the Oracle Database licensing guide and the Oracle Practice.

The mistake most teams make is trusting one source. A clean script output and a tidy CSI list can still hide a six figure compliance gap. The three options below each answer a different question.

What are the three ways to check Oracle license information?

Oracle does not give buyers a single screen that says what you own and what you use. You assemble that picture from three sources. Each has a purpose and a blind spot.

What does each source actually tell you?

Think of entitlement and deployment as two separate ledgers. One source reports the legal grant. Two report what is installed and switched on.

• Ordering documents: the legal entitlement. Quantities, metrics, and use limits you agreed to.
• LMS scripts and OEM: deployed usage. What is installed and which features are active.
• CSI portal: the order and support history. Useful for tracing what was bought and when.

Why do you have to reconcile all three?

Usage above entitlement is a compliance gap. Entitlement above usage is shelfware you are paying support on. You only see both by laying the three sources side by side.

Oracle reads the same gap during an audit. Building the view first lets you control the narrative rather than react to theirs.

How do Oracle LMS measurement scripts report usage?

The Oracle License Management Services scripts query the data dictionary and feature usage views. They are the most precise picture of deployed usage, and the most dangerous to share without review.

What do the scripts collect?

The standard collection reads DBA_FEATURE_USAGE_STATISTICS, options usage, and pack access. It captures Partitioning, Diagnostics Pack, Tuning Pack, and similar high cost options that switch on quietly.

• Options and packs: any separately licensed feature that has been used since install.
• Processor counts: the cores Oracle will multiply by the core factor.
• Edition and version: needed to map to the right price list metric.

Where do the scripts mislead buyers?

Feature usage statistics record a feature as used even when a single test query touched it once. The Oracle Database Licensing Information manual is the reference for what each option requires, and it rarely matches a raw script flag.

Review every flag before anyone outside the team sees it. A used flag is the start of a conversation, not a confession.

A clean script and a tidy support portal can still hide a six figure gap. The truth lives where all three sources disagree.

What does Oracle Enterprise Manager show about licensing?

Oracle Enterprise Manager, often called OEM or Cloud Control, includes a licensable management view. It is convenient and it is also a frequent source of accidental non compliance.

Why is Enterprise Manager itself a license risk?

Many OEM packs are separately licensed. Database Lifecycle Management and Diagnostics features inside the console need their own grants. Teams enable them to monitor estates and create exposure.

How does OEM differ from the LMS scripts?

OEM gives a live dashboard. The scripts give a point in time export Oracle trusts. For an audit baseline, the script export carries more weight, so use OEM for monitoring and the scripts for evidence.

How do you read entitlements in the My Oracle Support portal?

The Customer Support Identifier, or CSI, ties your support contracts to your orders. The portal lists what you bought, but not always the full legal terms.

What can the CSI view confirm?

It confirms active support, the products under that support, and renewal dates. It is the fastest way to map which entitlements are still on maintenance.

• Active CSIs: which contracts are current and which lapsed.
• Supported products: the line items still drawing support fees.
• Renewal dates: the clock that drives every negotiation.

What does the portal not tell you?

It rarely shows use limits, territory restrictions, or migration rights. Those live in the signed ordering document. Always pull the original contract before you trust a portal summary.

Suggested reading

• Oracle Database licensing guide. Cross vendor reading from the wider library.
• Oracle core factor table explained. Cross vendor reading from the wider library.
• Oracle ULA comprehensive guide. Cross vendor reading from the wider library.

What to do next

1. Pull every signed Oracle ordering document and build an entitlement ledger.
2. Run the current LMS scripts in a controlled window and keep the output internal.
3. Audit Enterprise Manager for licensable packs that were switched on for monitoring.
4. Reconcile the CSI portal order history against your entitlement ledger.
5. Flag every used option that lacks a matching grant and assign an owner.
6. Decide which gaps to remediate and which to fold into the next renewal.
7. Repeat the reconciliation quarterly so no surprise appears in an audit.

Frequently asked questions

Does running an LMS script trigger an audit?

No, running the scripts internally does not contact Oracle. The risk is sending raw output to Oracle before you review every feature usage flag and confirm it reflects real production use.

Where is my actual Oracle entitlement defined?

Your entitlement lives in the signed ordering documents and the master agreement. The portals report usage and orders, but the legal grant and its use limits sit only in those contracts.

Can Enterprise Manager put me out of compliance?

Yes, several Enterprise Manager packs are separately licensed. Enabling Diagnostics or Lifecycle Management features for monitoring can create exposure if you do not hold the matching grants.

How often should I reconcile the three sources?

Reconcile at least quarterly and always before a renewal or a suspected audit. A current baseline lets you control the position rather than scramble when Oracle requests a measurement.

Is the CSI portal enough on its own?

No, the CSI portal shows orders and support status but not use limits or territory rights. Always read the original ordering document alongside the portal summary before drawing conclusions.

What is the single biggest reporting mistake buyers make?

Trusting one source. A clean script, a tidy console, or a neat CSI list each tells part of the story. Compliance gaps appear only where the three sources disagree.