How to Check Oracle License Information — Three Options for IT and Procurement

The Oracle License Visibility Problem

Oracle licensing is opaque by design. The base database license covers a narrower set of features than most IT teams assume. Options, management packs, and add-on products each carry separate license requirements, and the boundary between what is included and what requires additional licensing is not always clear from the product interface. A DBA enabling database features for performance tuning may be creating a license obligation without knowing it. An application deployment may pull in Oracle Java or middleware components that require separate subscriptions.

The financial consequences of this opacity are significant. Oracle's annual support fee — charged at a percentage of the perpetual license value — increases by 8% per year. A compliance gap that goes undetected for three years does not simply cost three years of license fees; it costs three years of escalating support on the unlicensed deployment, with the gap itself compounding year on year.

The only effective counter to this is visibility. The three methods below are the practical tools for obtaining that visibility — and each serves a different purpose in a complete Oracle license management programme.

Option 1: The Oracle LMS Script Route

Oracle License Management Services (LMS) is the team that conducts Oracle's formal licence audits. When Oracle initiates an audit, LMS sends a set of data collection scripts to your environment. These scripts interrogate the Oracle data dictionary and system views to produce a technical snapshot of what is deployed, what features have been used, and what hardware the software runs on. Oracle then maps this data against your entitlements to produce an audit finding.

What many Oracle customers do not know is that these scripts are available through Oracle's My Oracle Support portal. You can download them, run them in your own environment, and review the output before Oracle does. This proactive approach gives you the same view of your estate that Oracle LMS would have in a formal audit, but in a context where you have time to analyse the findings, remediate gaps, and plan your response.

Why This Is the Most Comprehensive Method

The LMS scripts are designed to capture everything Oracle considers relevant to a compliance assessment. This includes the database edition and version, all enabled database options, feature usage history from the DBA_FEATURE_USAGE_STATISTICS view, hardware configuration including processor and core details, virtualisation environment data, and the deployment topology across your estate. No single SQL query or portal view captures the full breadth of data that the LMS scripts collect.

Running the LMS scripts proactively is the gold standard for Oracle license assessment, and it is the approach Redress Compliance uses as the foundation of every Oracle license review we conduct. The output provides a complete technical picture from which a licence gap analysis can be prepared against your Oracle contract entitlements.

The Operational Considerations

The LMS scripts require DBA-level access to each Oracle database in scope. They run as read-only queries and do not modify any configuration. Each database is assessed individually, so for organisations with large Oracle estates, the collection process needs to be planned and managed across the server inventory. The output files should be reviewed by someone with both technical Oracle knowledge and an understanding of Oracle licensing rules — the raw data alone does not constitute a compliance assessment; it is the input to one.

Option 2: Internal SQL Self-Assessment

For IT teams that want to maintain an ongoing view of Oracle deployment without running a full LMS script collection, a targeted set of SQL queries against Oracle's system views provides a practical monitoring capability. This approach is faster to execute than a full LMS collection, can be integrated into routine DBA processes, and can be automated as part of a continuous compliance monitoring programme.

The Key Views to Query

Oracle provides several system views that expose information directly relevant to license compliance. The V$OPTION view shows which database options are currently installed and enabled, providing an immediate snapshot of the options profile for any given database. Any option showing as TRUE in V$OPTION is a potential licence obligation if it falls outside your base license entitlement.

The DBA_FEATURE_USAGE_STATISTICS view is more commercially significant than V$OPTION because it records actual usage history, not just current installation state. Oracle's position in audits is that historical feature usage creates a licence obligation — a feature used once three years ago and never since still appears in the feature usage data and will be included in an Oracle audit claim unless it can be specifically addressed. Reviewing this view regularly, and understanding what each feature entry means commercially, is the most important ongoing compliance monitoring activity for Oracle database deployments.

The control_management_pack_access database parameter controls which Oracle Enterprise Manager management packs are available. The Diagnostics Pack and Tuning Pack are among the most commonly unlicensed Oracle features, partly because they are presented as available in Oracle Enterprise Manager without any visible restriction. Checking this parameter is a quick and high-value step in any Oracle compliance review.

Java SE — a Separate Inventory Challenge

Oracle's Java SE licensing changed fundamentally in January 2023. The new subscription model is priced per employee across the organisation, not per installation, for any organisation that has Oracle Java SE deployed anywhere in its environment. The compliance question begins with a thorough inventory of all JDK installations across the server estate — including application servers, middleware platforms, and any infrastructure that runs Java-based software.

This inventory cannot be done through Oracle database queries alone. Java SE deployments are often delivered through Oracle middleware products including Oracle WebLogic, Oracle Forms, and Oracle Application Server, as well as through direct installation. A complete Java SE compliance check requires a server-level inventory scan of all Java installations, with specific identification of which installations are from Oracle's distribution versus alternatives such as Eclipse Temurin, Amazon Corretto, Azul Zulu, or other OpenJDK distributions that do not carry Oracle Java SE licensing requirements.

Option 3: The My Oracle Support Portal

The first two methods tell you what you have deployed. The My Oracle Support (MOS) portal tells you what you have licensed. The portal is the authoritative source for Oracle's view of your support entitlements, and reconciling the deployment data from Options 1 and 2 against the MOS entitlement record is the core of any Oracle license gap analysis.

Navigating the MOS Entitlement Data

Log in to My Oracle Support at support.oracle.com and navigate to the My Account section to access your Support Identifiers. Each CSI (Customer Support Identifier) number corresponds to a set of licensed products under active support. The products and quantities listed under each CSI represent Oracle's record of what you have purchased and what is covered by your current support agreement.

This data is particularly useful for two purposes. First, it provides the baseline against which you can assess whether all deployed Oracle products have active support — which is a prerequisite for Oracle to recognise a licence as valid during an audit. Second, it identifies products that may be under support but no longer deployed, representing an opportunity to reduce support costs at the next renewal cycle.

What the MOS Portal Does Not Show

The MOS portal shows support contract data, but it is not a complete licence entitlement record. Support contract data reflects what Oracle's support systems have recorded, which may not capture all historical purchases, special contractual terms, or product-specific deployment restrictions. The authoritative entitlement record is the original Oracle ordering documentation — the contracts, order forms, and ordering documents that specify the exact metric, quantity, version restrictions, and any special terms for each product you have purchased.

For organisations with legacy Oracle contracts or complex purchasing histories involving multiple business units or mergers and acquisitions, the entitlement reconciliation process requires careful review of the contract documentation, not just the MOS portal. The portal is a useful starting point and a cross-reference tool, but it cannot replace the contract record.

Support Renewal Notices as a Reference

Oracle's support renewal notices list all products under active support with quantities and annual support fees. These notices are a useful supplementary reference for understanding the current support landscape, particularly for organisations that have not recently reviewed their full Oracle contract portfolio. They do not provide the full entitlement detail available in the original contract documents, but they give a quick snapshot of what Oracle currently bills you for and what products Oracle considers active in your environment.

Using All Three Methods Together

The most effective Oracle license programme uses all three methods as a layered approach. The LMS scripts provide the comprehensive technical baseline — the data that captures everything Oracle would collect in a formal audit. The SQL self-assessment queries provide ongoing monitoring between formal reviews, enabling the IT team to track changes in the deployment profile as infrastructure evolves. The MOS portal provides the entitlement baseline against which deployment data is reconciled to identify gaps and over-licensing.

Combining these three methods produces a complete Oracle compliance picture: what you have deployed, what you have licensed, and where the gaps lie. This is the foundation for three distinct value activities: remediating compliance gaps before they become audit findings; identifying over-licensed positions to reduce costs at renewal; and entering renewal negotiations with an accurate, current understanding of your Oracle position rather than relying on Oracle's claims and models.

Frequency and Triggers

A formal Oracle license review using the LMS script methodology should be conducted at minimum annually, ideally timed to inform the upcoming support renewal negotiation. The SQL self-assessment queries should be part of routine DBA monitoring on a monthly or quarterly basis. Out-of-cycle reviews are warranted any time your Oracle environment changes materially — a cloud migration, a virtualisation platform change, a significant application deployment, an M&A transaction, or any event that alters the deployment footprint of your Oracle software.

Given that Oracle support fees increase by 8% per year and audit claims compound over time, the cost of maintaining a regular, informed compliance programme is always lower than the cost of responding to an audit without current knowledge of your own position.

The Risk of Not Checking

Organisations that do not have a current, accurate view of their Oracle license position are systematically disadvantaged in three ways. In an audit, they cannot distinguish between genuine compliance gaps and Oracle claims that are inflated, technically incorrect, or based on non-contractual assumptions. In renewal negotiations, they cannot verify Oracle's claims about their entitlement usage and cannot identify over-licensed positions that could reduce renewal costs. And in day-to-day operations, they accumulate silent non-compliance as the environment changes — creating an exposure that grows with every year Oracle support fees compound.

The investment in maintaining visibility of your Oracle license position is modest compared to either the audit exposure it prevents or the negotiation value it enables. The three methods described here — LMS scripts, SQL self-assessment, and the MOS portal — are practical tools accessible to any organisation with Oracle in its environment.