The Oracle LMS letter is the start of a structured discovery program. The first 72 hours fix the scope, the script, and the chain of communication. This article maps the response.
An Oracle audit starts with a letter from Oracle License Management Services (LMS), now folded into the Oracle Software Investment Advisory (SIA) practice. The letter cites the audit clause inside the OMA or OLSA and requests a kickoff call. The clause grants Oracle the right to verify license use, but every other parameter is open to negotiation.
The first 72 hours fix three things. The scope of the audit (products, entities, geographies). The script (who talks to Oracle, in what form, with what evidence). And the chain of communication (no direct DBA to LMS contact, no informal email threads).
Read this alongside the Oracle knowledge hub, the Oracle audit services, the audit landing page, and the Vendor Shield subscription.
The Oracle LMS letter is a templated document. It cites the audit clause, requests a kickoff call, lists the products in scope, and asks for the verification scripts to be run within a defined window.
The 72 hour window sets the tone of the audit. A clean response inside 72 hours establishes you as a structured customer and pulls Oracle into a process led by your counsel and your advisor.
Every Oracle audit lever traces back to two questions. What is the audit scope? And who controls the data Oracle sees?
| Scope dimension | Oracle opening position | Buyer side counter |
|---|---|---|
| Product scope | All Oracle products deployed | Only the products named in the letter, by product name and version |
| Legal entity scope | All affiliates and subsidiaries | Only the contracting entity and the entities named on the order |
| Geographic scope | Global | Specific data centers or regions named on the order |
| Time period | Inception to today | The current support term only |
| Script control | Oracle runs LMS scripts | Customer runs scripts under observation, output reviewed by counsel |
The Oracle audit playbook has eight or nine repeat findings. Knowing them in advance lets the buyer side prepare a position paper before the kickoff.
An Oracle audit settles on remediation, not list. The math runs through three stages. Effective license position, gap by product, and settlement at a negotiated discount.
The ELP captures what the customer is entitled to, what is deployed, and what is missing.
An accurate ELP cuts the Oracle audit position by 20 to 60 percent on most engagements. Most internal license records under count entitlements because they miss ULA certifications, migrated licenses, and license bank credits.
| Line item | Oracle opening | Buyer side position | Settlement |
|---|---|---|---|
| Partitioning | 16 processor at 11,500 USD list | 4 processor, cluster pinned | 6 processor settled |
| Diagnostics Pack | 16 processor at 7,500 USD list | 0 processor, no AWR queries | 0 processor settled |
| Java SE Universal | 12,000 employees at 15 USD per month | 4,000 user perimeter | 6,500 employee 1 year subscription |
| Standby database | 4 processor | 10 day failover rule | 0 processor settled |
The eight step checklist takes an Oracle audit from the LMS letter to a controlled settlement position.
The typical Oracle audit runs 4 to 9 months from the LMS letter to settlement. Scope fights take 30 to 60 days at the front, script execution and review takes 60 to 120 days in the middle, and the commercial settlement takes 60 to 120 days at the back.
A controlled audit with disciplined scope and script work lands at the shorter end. An uncontrolled audit, where Oracle gets early script access, often extends past 12 months.
The audit clause grants Oracle the right to verify license use. It does not grant LMS the right to run scripts directly on customer systems. The buyer side counter is to run the scripts internally, output to counsel, output to LMS under a defined scope.
This is the single most important lever in the first 72 hours. Once LMS owns the script output, the buyer side loses 60 percent of the settlement leverage.
Oracle Database licensing allows a failover instance to run on a designated standby host for up to 10 separate days in any 365 day period without requiring a separate license. The rule applies to a single failover environment, not active active.
Audit findings frequently challenge the 10 day rule. Document the failover events, the host, and the duration to defend the position.
The Java SE Universal Subscription, introduced January 2023, counts every employee, contractor, and temporary worker, not just Java users. The audit position lists the company headcount as the subscription quantity.
The buyer side counter documents the legitimate Java installation perimeter, the OpenJDK migration path, and the desktop Java exit position. Customers on a pre 2023 NUP or processor Java contract retain that metric.
The ELP captures what the customer is entitled to (licenses purchased, ULAs certified, migrations completed), what is deployed (current install base), and the gap. An accurate ELP cuts the Oracle audit opening position by 20 to 60 percent on most engagements.
Most internal license records under count entitlements because they miss ULA certifications, license bank credits, and migrated licenses across legal entities.
Redress runs Oracle audit defense inside the Vendor Shield subscription, the audit defense services, and on engagement basis where the LMS letter has already landed. The first session inside the 72 hour window costs nothing.
The output is a scope position letter, a script discipline protocol, an effective license position, a position paper, and a settlement memo. The engagement is led by a former Oracle commercial professional on the buyer side.
Redress runs Oracle audit advisory inside the Vendor Shield subscription, the audit services, the Software Spend Assessment, and the Renewal Program.
Read the related Oracle hub, the Oracle services page, the audit landing, the complete audit playbook, the ULA negotiation guide, the Java licensing guide, the licensing consultants guide, the benchmarking page, the about us page, and the contact page.
Buyer side reference on Oracle LMS audits. Scope discipline, script control, effective license position, the eight common findings, and the seven levers procurement carries to settlement.
Independent. Buyer side. Written for CIOs, CFOs, procurement leaders, and licensing professionals carrying an active LMS letter or a likely one. No Oracle kickback. No conflict on the table.
Open the white paper in your browser. Corporate email only.
Open the Paper →The first 72 hours decide the Oracle audit. Once a DBA runs an LMS script informally, the buyer side loses two thirds of the settlement leverage. The discipline is procedural, not technical.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
LMS letter patterns, scope tactics, script discipline notes, Java perimeter math, ULA settlement plays, and audit defense lessons from every Oracle engagement we run on the buyer side.
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.
