A step-by-step guide from Redress Compliance covering what data to collect, how to run the Oracle LMS Collection Tool, and how to share results securely.
Enter your details below to view the full guide and interactive checklist. Your completed checklist will be sent to your Redress project lead.
This guide outlines the data collection process required to support your Oracle licence optimisation engagement with Redress Compliance. Accurate and complete data is essential. It allows us to assess your full Oracle deployment, identify optimisation opportunities, and prepare the best possible commercial options for your ULA renewal, certification, or licence position.
The primary collection tool is the Oracle LMS Collection Tool, a read-only, non-intrusive script provided by Oracle. It is safe to run on production systems.
The LMS Collection Tool is the standard Oracle-provided script used to discover what Oracle software is installed across your environment. It can analyse all Oracle software listed in the User Manual, including all Database editions, all Middleware products, WebLogic, WebCenter, OBI EE, Identity Management, and all licensable options and packs.
| Oracle Product Area | Collection Method | Action |
|---|---|---|
| Oracle Database (all editions) | Run LMS Collection Tool | LMS Script |
| Oracle Middleware / WebLogic / WebCenter | Run LMS Collection Tool | LMS Script |
| Oracle Business Intelligence (OBI EE) | Run LMS Collection Tool | LMS Script |
| Oracle Identity & Security Products | Run LMS Collection Tool | LMS Script |
| Oracle E-Business Suite (EBS) | Run LMS Tool with --EBS parameter | LMS Script |
| Oracle GoldenGate | Manual template (source & target) | Request Template |
| Oracle Java SE | Manual inventory (path, version, patch) | Request Template |
| Cloud Deployments (OCI / AWS / Azure / GCP) | Cloud template (Excel) | Request Template |
The download contains the LMS script files and the User Manual with detailed step-by-step instructions for each Oracle product area.
Download from Redress BoxRun the LMS Collection Tool on every server hosting an Oracle Database instance. This includes all editions (Standard, Enterprise, Express) and all environments (Production, Non-Production, Test, DR). The Database script is usually very quick, completing in minutes per server.
Run the LMS Collection Tool on all servers where Oracle Middleware is installed. This includes WebLogic Server, WebCenter, Oracle HTTP Server, and related Fusion Middleware products. Note: the FMW scan takes longer than the Database scan as it searches the filesystem for Oracle binaries.
GoldenGate is not covered by the LMS script. Request the GoldenGate template from Redress. We need hardware details (processor type, sockets, cores) for both the source and target servers involved in GoldenGate replication. GoldenGate is licensed on the physical hardware of both ends.
Run the LMS Collection Tool on the servers hosting OBI EE. The standard LMS script will detect the BI installation and report licensable components.
Run the LMS Collection Tool on all servers hosting Oracle Identity Management, Access Manager, or related security products.
Run the LMS Collection Tool with the --EBS parameter on the database server hosting the EBS database. This collects application licensing information including application user counts, module usage data, concurrent users, and licensed application products.
There is no Oracle-provided collection script for Java. We ask you to provide the following for all Java installations: install path (where the Java binaries are installed), Java distribution, version, and patch level. Request the Java template from Redress if needed.
For any Oracle software running in the cloud, request the Cloud Template (Excel) from Redress. We need details including: cloud provider, instance type, vCPU/OCPU count, whether multi-threading/hyper-threading is enabled, and whether Multi-AZ is configured. This applies to all cloud providers.
For VMware, Oracle requires licensing of ALL physical hosts in ALL ESXi environments, not only where Oracle is running. Run RVTools (or equivalent) against your vCenter and export the full output. We need data from every ESXi host in every cluster, regardless of whether Oracle VMs exist on that host.
For Hyper-V, Oracle licensing applies only to servers in the cluster(s) where Oracle is running. This is narrower than VMware scope. Provide hardware details (processor type, sockets, cores) for all servers in the relevant cluster(s).
Use this checklist to confirm all required data has been collected and shared with Redress Compliance. Select Yes, No, or N/A for each item. Your completed checklist will be submitted to your project team.
All collected data (LMS script outputs, RVTools exports, completed templates, ordering documents) must be shared securely with Redress Compliance. There are two options:
Yes. The script is completely read-only and non-intrusive. In 25+ years of Oracle licensing advisory, we have never encountered a single performance issue caused by running the LMS Collection Tool.
The Database script is usually very quick, completing in minutes per server. The Fusion Middleware (FMW) script takes longer as it scans the filesystem for Oracle binaries. Clients with 2,000+ databases have completed full collection in a few hours using automation tools.
In 99% of cases, script issues are due to insufficient privileges. The script needs to be run as root (Linux/Unix) or Administrator (Windows). If you encounter any issues, contact your Redress project lead immediately.
Please inform your Redress project lead about any DR environments that are currently powered off. We need to account for these in the compliance assessment even if we cannot collect data from them directly.
Contact your Redress project lead for guidance. We have templates and collection methods for all Oracle-licensable environments.
Once you have completed all items above, submit your checklist to your Redress project team.
Your completed checklist has been sent to your Redress Compliance project team at [email protected]. Your project lead will follow up with you shortly.
If you have any questions about the data collection process, encounter issues running the LMS tool, or are unsure whether a particular environment is in scope, please contact your Redress project lead immediately. We are available throughout the data collection phase to assist and troubleshoot.
Email: [email protected]
Phone: +1 (239) 402-7397