What Is Oracle ReviewLite?
Oracle ReviewLite is a proprietary SQL script developed and maintained by Oracle's Licence Management Services (LMS) team. It is the primary tool Oracle uses to collect Oracle Database licensing-relevant data during formal compliance audits and Unlimited License Agreement (ULA) certification events. The script queries Oracle system tables and data dictionary views to produce a structured output report that documents what Oracle Database products are installed, what optional features and packs have been used, how many users have access, and the physical hardware configuration of the servers where Oracle Database is running.
The "Lite" designation in the name distinguishes this tool from Oracle's full LMS Collection Tool, which covers a broader range of Oracle products including Oracle Middleware and Oracle Applications. ReviewLite is scoped specifically to Oracle Database products: Oracle Database Enterprise Edition, Standard Edition, Standard Edition 2, and the various database options and management packs that carry separate licence fees when used.
ReviewLite is not publicly downloadable. It is distributed by Oracle's LMS team to customers who are under active audit, or it can be accessed through My Oracle Support (MOS) by customers who wish to conduct a voluntary self-assessment. It is not available from any third-party source — only Oracle LMS can provide an authentic, current version of the script.
What Data Does Oracle ReviewLite Collect?
Understanding what data ReviewLite collects is essential before you agree to run it and share the output with Oracle. The script is comprehensive and designed to leave no significant licensing exposure undiscovered. It captures information across several key areas:
Oracle Database Product Data
- Oracle Database version, edition (Enterprise, Standard Edition 2, etc.), and patch level for every database instance on the scanned server
- Oracle Database options installed and enabled — including partitioning, Real Application Clusters (RAC), Advanced Security (TDE), Multitenant, and others that carry separate licence fees
- Oracle Management Packs that have been accessed — including Diagnostics Pack, Tuning Pack, and Data Masking and Subsetting Pack — even if accessed historically through Enterprise Manager
- Oracle Database Vault, Label Security, and other separately licensed security options
User and Access Data
- Count of database user accounts configured in each Oracle instance
- Active users (those who have logged in within a recent period)
- User account attributes relevant to Named User Plus licence counting
Hardware and Processor Data
- Physical server hardware specifications — processor count, physical core count per socket, total socket count
- Processor type and model, relevant to Oracle's core factor table calculation
- Virtualisation layer information — whether the database runs on bare metal, in a VM, or in a container
- NUMA topology and CPU architecture data relevant to partitioning policy calculations
The combination of option usage data and hardware data is what makes ReviewLite output so commercially significant in an audit context. Oracle can cross-reference the options detected against your licence entitlements in a matter of minutes. Every option that appears in the ReviewLite output for which you do not hold a licence represents an unlicensed use finding — and Oracle will price each finding at current list price, then multiply it by 22% annual support fees, and seek back-payment for the entire audit period.
When Oracle Requests ReviewLite
Oracle's LMS team requests ReviewLite output in two primary scenarios:
During a Formal Compliance Audit
When Oracle initiates a licence compliance audit — typically by sending a formal audit notification letter to the CIO or CLO — LMS will follow up with a request to run ReviewLite on all servers in scope. Oracle will provide the script directly and request that it be run against every Oracle Database instance in your environment. The output files are then transmitted to Oracle's LMS team for analysis.
Enterprises under formal audit are not legally obligated to run ReviewLite — your obligations under the Oracle Master Agreement typically require you to provide access to allow Oracle to verify compliance, but the specific form of that verification is often negotiable. Many organisations, particularly those with known compliance exposure, choose to run their own internal assessment first, remediate any gaps they identify, and then provide a curated, accurate picture to Oracle. This requires independent advisory support to be done safely.
During ULA or PULA Certification
When an Oracle ULA (Unlimited License Agreement) approaches its certification date, Oracle will request that customers run ReviewLite as part of the certification process. The ReviewLite output establishes the "peak deployment" count under the ULA — the number of Oracle Database processor licences that will be certified as your perpetual entitlement when the ULA expires. This certification count becomes your licence baseline going forward, so accuracy is commercially critical in both directions: undercounting creates future compliance exposure; overcounting permanently inflates your support cost baseline (and Oracle's annual support fees increase by 8% on that inflated number every year thereafter).
Received a ReviewLite request from Oracle LMS?
Do not run or share ReviewLite output without independent advisory review. Our ex-Oracle LMS advisors will assess your position before Oracle sees the data.Using ReviewLite for Self-Assessment
One of the most valuable uses of Oracle ReviewLite is proactive self-assessment — running it on your own Oracle Database estate before Oracle does, to understand your current licensing position and identify any compliance gaps that need to be resolved. Oracle customers can download ReviewLite from My Oracle Support (MOS) at any time without triggering an audit or notifying Oracle. Running it yourself in advance of an audit, a ULA certification, or a major Oracle renewal negotiation gives you critical intelligence that Oracle will also obtain — but with time to act on it before the commercial conversation begins.
Proactive ReviewLite self-assessment is particularly valuable in three scenarios. First, if you are approaching a ULA certification date and want to optimise the deployment count you certify — maximising deployment of covered products before the certification event, since every additional deployment under a ULA is free (the support fee is fixed regardless of deployment volume, so maximising deployment before certification is always in the customer's interest). Second, if your Oracle environment has grown organically and you are not confident that all option and pack usage has been tracked against licence entitlements. Third, if you are in a support renewal negotiation and want to enter that conversation with a complete, accurate picture of your Oracle footprint.
The Management Pack Risk: Oracle's Most Common Audit Finding
The most commercially significant category of ReviewLite findings in practice is Oracle Management Pack usage. Oracle's Diagnostics Pack, Tuning Pack, and other management packs are licensed separately from Oracle Database Enterprise Edition. However, these packs are enabled by default in Oracle Enterprise Manager and are used routinely by DBAs for performance monitoring, query tuning, and database diagnostics — often without the DBA knowing that each use creates a separate licence requirement.
The Oracle Diagnostics Pack, for example, is required for any use of the Automatic Workload Repository (AWR), Automatic Database Diagnostic Monitor (ADDM), and Active Session History (ASH) — tools that are among the most commonly used for Oracle Database performance management. These features appear enabled in ReviewLite output for the vast majority of Oracle Database Enterprise Edition installations, and the majority of those installations do not hold a Diagnostics Pack licence. This creates one of Oracle's most reliable audit findings, and it appears in ReviewLite output with complete clarity.
Immediate Action: If your DBAs use Oracle Enterprise Manager for performance monitoring, run a ReviewLite self-assessment immediately. Pack usage detected there will appear in any future Oracle audit — and remediation requires either purchasing the licences or disabling the features before Oracle sees the data.
Oracle Partitioning Option: Another Common ReviewLite Flag
Oracle Partitioning is a separately licensed Database Option for Oracle Database Enterprise Edition, costing approximately $17,500 per processor licence at current list price. ReviewLite detects partitioning usage by querying whether any Oracle Partitioning features have been enabled or used in each database instance. Partitioned tables, partitioned indexes, and any use of partition-related syntax triggers a positive detection in the ReviewLite output. This is a high-value finding for Oracle's LMS team — in environments with dozens of Oracle Database instances, unlicensed partitioning usage can add millions of dollars to an audit claim.
How to Respond When Oracle Requests ReviewLite
Receiving a ReviewLite request from Oracle LMS — whether as part of a formal audit or a ULA certification — should be treated as a significant commercial event, not a routine administrative task. The steps to take immediately upon receiving such a request are:
- Do not run or share ReviewLite output immediately. You need time to understand your position before Oracle does. Review your Oracle Master Agreement to understand your contractual obligations and the timeline for compliance.
- Engage independent Oracle licensing advisory support. Before any data is shared with Oracle, an independent advisor who understands Oracle's LMS methodology should review your Oracle estate and model the potential findings against your licence entitlements.
- Run ReviewLite internally first. Conduct a self-assessment using the same script Oracle will use, review the output in detail, and identify all potential compliance gaps before they appear in Oracle's analysis.
- Remediate where possible before the formal audit output is produced. Some compliance gaps — particularly unused database options that were enabled but not actively in use — can be disabled before the audit script is formally run for Oracle. Disabling an option that was never used in production is a legitimate remediation step that reduces audit exposure.
- Define the audit scope carefully. Oracle's initial request is often for broad scope — all Oracle Database instances in the organisation. Your Master Agreement may provide rights to limit the scope or negotiate the terms of the audit. An independent advisor can help you exercise these rights effectively.
Want to run ReviewLite proactively before your next renewal?
Redress Compliance can run an independent Oracle Database licensing assessment using the same methodology Oracle LMS applies — and help you fix what needs fixing before Oracle does it for you.Key Takeaways
- Oracle ReviewLite is an SQL script issued by Oracle LMS to collect Oracle Database configuration, option usage, and hardware data for licensing compliance purposes.
- It identifies every Oracle Database option and management pack ever enabled — including historical usage — which is the source of most high-value Oracle audit findings.
- Oracle requests ReviewLite during formal compliance audits and ULA/PULA certification events.
- Customers can access ReviewLite through My Oracle Support to conduct proactive self-assessments before Oracle initiates a formal review.
- Never share ReviewLite output with Oracle without first reviewing the results with independent Oracle licensing advisors — the output may reveal compliance gaps you need to address before the commercial conversation begins.
- The Oracle Diagnostics Pack, Tuning Pack, and Oracle Partitioning Option are the most common unlicensed-use findings that ReviewLite detects in enterprise Oracle Database environments.