The Oracle LMS measurement script dumps every option, every pack, and every feature ever touched on the database. Read it the way LMS reads it. The audit finding sits in the script, not in the cover letter.
The Oracle LMS measurement script is a single SQL collection bundle. It runs against the database, reads six core views, writes the output to a flat file, and ships the file to LMS. The data inside the file is the audit finding. The cover letter is decoration.
The buyer side that runs the script in a non production copy first, reads the option findings, and contains the exposure controls the audit. The buyer side that hands the file to LMS without preparation surrenders the finding.
The LMS collection script is a SQL bundle delivered as a zip. It contains a master script, six core SQL files, and an output formatter. The buyer side runs the master script as a privileged user against the target database. The output is a single flat file.
The script queries the data dictionary views that record option usage. It also reads the database instance metadata, the user list, the segment list, and the storage allocations. Nothing in the script writes or modifies data.
The script does not read user data. It does not read application tables. It does not read row level content from any schema. The audit data is metadata about feature deployment and configuration, not customer data.
The output file is a flat text file with one section per view. The file sits on the database server in a defined output directory. The customer transmits the file to LMS through the audit response process, usually as an email attachment or secure upload.
Before the file leaves the customer firewall, the buyer side has to verify the option findings, the feature usage dates, the user list, and the storage allocation. The buyer side that reads the file first sees the audit finding before LMS does.
Six data dictionary views drive every Oracle LMS audit finding. The buyer side that knows the six views can read the script output as fast as the auditor.
The v$option view lists every Oracle option installed on the database. The view records the option name and a flag showing whether the option is enabled. An enabled option does not prove usage but it proves the option is reachable.
This view records every feature touch on the database since the database was created. Each row carries the feature name, the first use date, the last use date, and the use count. The buyer side reads this view first because it drives the largest findings.
The user views capture every account that ever held privileges that match an option. Database Vault, Label Security, and Advanced Security findings often trace to a single privileged user grant. Removing the grant does not erase the finding.
The segment view captures every partitioned table, every compressed segment, and every encrypted tablespace. The view is the canonical source for Partitioning, Advanced Compression, and Advanced Security findings on the storage layer.
The instance views capture the database edition, the version, the cluster topology, and the platform. The script uses these views to detect Real Application Clusters deployment and to confirm Enterprise Edition versus Standard Edition installation.
| View | What it proves | Audit weight | Common finding |
|---|---|---|---|
| v$option | Option installed and enabled | Medium | Multitenant, RAC enabled |
| dba_feature_usage_statistics | Feature touched at least once | High | Diagnostic Pack, Tuning Pack |
| dba_users / dba_role_privs | Privileged grants | Medium | Advanced Security, Vault |
| dba_segments | Partition, compression, encryption | High | Partitioning, Advanced Compression |
| v$instance | Edition and cluster topology | Medium | Enterprise Edition, RAC |
| gv$instance | Cluster wide instance metadata | Medium | RAC node count |
Seventeen Oracle Database options and management packs sit behind the largest LMS findings. The buyer side that knows the list can read the script output in minutes and predict the finding before the auditor responds.
Partitioning, Diagnostic Pack, Tuning Pack, and Advanced Compression drive the majority of audit findings by value. Each of these options costs a meaningful percentage of the Enterprise Edition list price per processor.
Advanced Security, Label Security, and Database Vault sit in a data security cluster. The findings frequently chain together because a single privileged user grant can register all three.
Real Application Clusters, RAC One Node, and Active Data Guard sit in the high availability cluster. The findings register against v$instance, gv$instance, and feature usage statistics in combination.
Multitenant deployment shows up in v$option and feature usage. The Standard Edition database that ran a CDB before the customer noticed registers a Multitenant finding even though Multitenant is not licensable on Standard Edition.
The dba_feature_usage_statistics view is the longest memory in the script. The view records every feature touch from the moment the database was created. Oracle uses the first use date as the license obligation start point.
Every feature use registers a row with the first use date, the last use date, the use count, and the highest concurrent use. The recording is automatic. The customer cannot opt out of recording without breaking the database.
Oracle treats any attempt to purge or modify the feature usage tables as a license violation. The audit team will check the table for tamper evidence. A clean history on a long lived database raises a separate finding.
The buyer side reads the history from oldest to newest. A first use date in 2014 on a feature the customer claims is not in use suggests either dormant code, a former DBA test, or unattended product behavior. Each cause carries a different remediation.
Customers in a former Unlimited License Agreement often have feature usage history from the ULA period. The ULA certification process does not erase the history. Post certification LMS audits read the historical records and challenge the certified position.
The script output is a flat file. The buyer side reads it through three lenses. The option lens identifies the high value findings. The usage lens proves whether the option is in active use. The history lens shows the duration of exposure.
Any option flagged TRUE in v$option is reachable. The next question is whether the option has registered usage. Reachable plus unused is a defensible position. Reachable plus used is the finding.
Every option finding has a corresponding feature usage row. A Diagnostic Pack finding traces to ASH, AWR, or ADDM usage. A Partitioning finding traces to a partitioned segment in dba_segments.
Not every usage record proves licensable usage. Oracle Enterprise Manager touches features in the course of normal operation. Backup tools, monitoring agents, and DBA scripts can register a feature touch that is not user driven.
Where the usage is incidental, the buyer side documents the attribution. Where the usage is intentional but limited, the buyer side scopes the population. Where the usage is broad, the buyer side prepares the negotiation position before the file leaves the firewall.
The checklist takes the SAM manager from the LMS audit notice to a contained finding. The earlier the work starts, the wider the option set on the negotiation.
The Oracle License Management Services script is a SQL collection that reads the dba_feature_usage_statistics view, the v$option view, the dba_users view, and several option specific tables. The output captures every option that has ever been used since the database was created.
The dba_feature_usage_statistics view records when a feature was first used and when it was last used. The first use date proves the option was deployed. Oracle treats the first use date as the license obligation start point.
No. Oracle treats any attempt to purge or modify the feature usage tables as a license violation. The buyer side must contain exposure through option configuration and process control before LMS arrives.
The script captures Enterprise Edition options separately from Standard Edition features. A Standard Edition installation does not raise option findings, but the script still measures the database against Enterprise Edition usage.
Partitioning, Diagnostic Pack, Tuning Pack, Advanced Compression, Advanced Security, Real Application Clusters, and Multitenant carry the highest list price exposure. Touching any of these features once registers a usage record.
Redress runs the script in a non production copy first inside the Vendor Shield subscription. The team scopes the options that show usage, tests whether the usage is intentional or incidental, and contains the exposure before the script result leaves the customer firewall.
Median 28 percent recovery on the audit finding through option scoping, partition rules, ULA history tests, and feature usage attribution. The recovery requires the buyer side to read the script before LMS does.
The script is read only and runs in a few minutes on a healthy production database. The output is a flat file that the customer attaches to the audit return. The data inside the file drives the finding.
Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, and the Software Spend Assessment.
Read the related Oracle ULA decision framework, the Oracle Java licensing, the Oracle services, the benchmarking service, and the Benchmark Program.
Oracle ULA renewal timing, exit math, certification rules, and the buyer side moves that protect ULA outcomes.
Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.
Open the playbook in your browser. Corporate email only.
Open the Paper →The script is a confession. Read it before you hand it over. The auditor will not ask twice. The cover letter never says the words that the data already proves.
We run Oracle LMS script reviews before the audit data leaves the customer firewall. Median 28 percent recovery on the finding through option scoping, partition rules, and historical usage tests.
Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
