Oracle's LMS audit scripts don't just measure your compliance — they build the commercial case for Oracle's sales team. Every stage of the LMS process, from the initial notification letter through data collection, claim calculation, and settlement negotiation, is designed to maximise Oracle's financial outcome. Understanding what Oracle does at each stage — and what you are and are not obligated to provide — is the difference between a controlled compliance review and a seven-figure demand you pay under commercial pressure.
Oracle Licence Management Services — now partially operating under the Oracle Global Licensing and Advisory Services (Oracle GLAS) brand — is Oracle's internal audit organisation. Oracle presents LMS engagements as a mutual compliance review designed to help customers understand their Oracle licence position. This is not accurate.
Oracle LMS is a revenue-generating function. Its teams are incentivised on the value of compliance findings — the gap between what Oracle believes you owe and what you have paid. Every interaction with LMS, every piece of data you provide, every question you answer, and every document you submit is processed through the lens of Oracle's commercial objective: identify the largest defensible compliance gap and monetise it through back-licence fees, subscription conversions, or accelerated renewal deals.
Oracle's information asymmetry: Oracle's LMS team has conducted thousands of enterprise audits. They know exactly which deployment patterns create the largest compliance gaps, which questions reveal the most valuable upsell data, and which customers are most likely to settle quickly under commercial pressure. Your IT team responding ad hoc to Oracle's questionnaire is operating at a severe disadvantage. The only effective response is independent Oracle licensing expertise on your side from the first contact.
This is not to say that Oracle audits cannot be managed successfully — they can. But successful management requires understanding Oracle's playbook at every stage and responding deliberately, not reactively. The enterprises that pay Oracle's maximum claim are those that engaged with LMS directly, provided data without independent review, and negotiated settlement without knowledge of what Oracle's claim was actually based on.
Oracle sends a formal notification letter — typically to a senior IT executive, CISO, or General Counsel — invoking the audit clause in your Oracle licence agreement. The letter requests that the customer submit to a licence review and typically names an LMS account executive who will manage the process. The letter is formal in tone, references specific contract clauses, and creates an impression of legal obligation to cooperate fully and immediately.
Your contractual obligation to cooperate with an Oracle audit is real but narrower than Oracle's letter implies. Oracle's standard licence agreements require you to permit Oracle to audit your use of Oracle software and to provide reasonable assistance. They do not require you to respond within Oracle's requested timeframe, provide data in Oracle's preferred format, or permit LMS scripts to be run without your IT team's involvement and supervision. They do not require you to answer questions that go beyond documenting software usage — and Oracle frequently asks questions that serve sales intelligence purposes well beyond compliance measurement.
The first action is to engage independent Oracle licensing counsel before responding to Oracle's letter. The response to Oracle's notification letter sets the tone for the entire audit. An organisation that responds quickly with a cooperative "yes, we'll arrange access" gives Oracle everything it needs to run the process on Oracle's terms. An organisation that responds with a measured, professionally drafted acknowledgment that preserves its rights — while committing to a constructive process — changes the dynamic immediately.
Our audit defence team manages audit notification responses as the first engagement point. Read the Oracle Audit Defence Guide for a full analysis of your contractual rights.
The first 72 hours set the trajectory for the entire audit. Our Oracle Audit Defence specialists provide immediate support — audit notification response, rights assessment, and engagement strategy — from the moment Oracle's letter arrives.
Oracle's LMS team schedules a kick-off meeting to define the audit scope: which Oracle products, which geographies, which legal entities, and which infrastructure will be reviewed. Oracle uses this meeting to gather substantial intelligence about your environment — the number of servers running Oracle, the virtualisation platform, the database versions in use, the number of named users, and whether options like Diagnostics Pack, Tuning Pack, or Advanced Security are installed. This information directly informs Oracle's preliminary claim estimate before a single script is run.
The scoping meeting is where Oracle builds its preliminary model. Every piece of information you volunteer — the size of your VMware cluster, the number of employees using Java, the fact that you recently migrated to Oracle Database EE from SE2 — becomes an input into Oracle's preliminary claim calculation. You should attend this meeting with independent Oracle licensing advisors who understand what information is genuinely required by the audit scope and what goes beyond it.
Scope limitation is a critical defence at this stage. If Oracle's audit scope in your licence agreement is limited to specific products, you are not obligated to expand it. Negotiating the audit scope — which products, which entities, which infrastructure — can materially reduce Oracle's access to data and therefore the size of the resulting claim. Oracle will typically push for the broadest possible scope; your objective is a scope that is contractually justified and operationally manageable.
Oracle LMS requests permission to run their audit scripts on your infrastructure. The primary tools are USMM (Usage Monitoring and Measurement) and Review Lite — Oracle-authored scripts that collect detailed information about Oracle software installations, configuration, and hardware. For Java audits, Oracle may use Oracle Licence Review (OLR) or request data directly from asset management systems. For VMware environments, Oracle frequently requests vCenter exports alongside the host-level script output.
USMM scripts collect far more data than required for pure compliance measurement. They capture: Oracle product installations and version information; database instance names and configurations; option and management pack installation status (including enabled diagnostic packs, tuning packs, and advanced features); hardware configuration including processor model, socket count, and core count; VMware cluster membership; and various database parameter settings that indicate feature usage. Some of these data points are relevant to compliance measurement. Others are relevant exclusively to Oracle's sales intelligence — understanding your deployment architecture, growth trajectory, and technology choices for use in the next commercial conversation.
The Diagnostics Pack trap: USMM scripts identify whether Oracle Diagnostics Pack and Tuning Pack are enabled in your database environment. These options are enabled by default in many Oracle Database installations through the CONTROL_MANAGEMENT_PACK_ACCESS parameter, which defaults to 'DIAGNOSTIC+TUNING'. Enterprises frequently discover during an LMS audit that they have been using Diagnostics Pack features (AWR, ADDM, ASH) without knowing they require a separate licence — a compliance gap that adds Diagnostics Pack licence cost across every processor in scope. Oracle Diagnostics Pack is accidentally enabled in over 40% of enterprise environments we review.
You should review any script Oracle proposes to run before granting permission. USMM scripts are not secret — your independent Oracle licensing advisors will know their content. You are entitled to understand what data will be collected, to have your own IT team present during script execution, and to receive the raw script output before Oracle processes it. The raw output is your baseline for challenging Oracle's interpretation of the data.
You should also conduct your own independent inventory before Oracle's scripts run. Knowing your Oracle deployment before LMS does — which products are installed, which options are enabled, which instances are active, and which can be decommissioned — gives you the ability to remediate some issues before the audit measurement and to challenge Oracle's findings from an evidence base, not from a reactive position.
Oracle's LMS team processes the script output against your licence entitlements to calculate the compliance gap. This analysis applies Oracle's interpretation of the Core Factor Table, the soft partitioning policy for virtualised environments, the Named User Plus minimums for your deployment type, and the installed options to produce a total shortfall in processor licences, NUP licences, and option licences. The gap is then valued at Oracle's current list price, producing the initial claim figure.
The claim calculation is where the largest errors and the most aggressive assumptions typically appear. Common calculation errors that your independent advisors should challenge include: incorrect processor identification leading to wrong Core Factor application; inclusion of development and test environments that may be covered by separate development licences; double-counting of instances across clustered environments; options attributed as "used" based on installation rather than actual usage; and cluster membership calculations that include hosts not genuinely running Oracle software.
Oracle's claim calculation is a proposal, not a legal determination. Your compliance review specialists should independently recalculate the compliance position from the same raw data before accepting Oracle's figure. In our experience, Oracle's initial claim is 3–5× what the customer actually owes after independent challenge of the calculation methodology.
Oracle presents a draft compliance report to your organisation, typically in a meeting with both LMS and Oracle's sales team present. The report states Oracle's compliance position: the number of licences you have, the number Oracle believes you need, and the shortfall. It often includes a remediation proposal — a list of products and quantities you can purchase to resolve the audit. The meeting is structured to create urgency and commercial pressure: the "audit" phase is presented as concluded, and Oracle positions the next step as a commercial discussion about how to remediate the gap.
The draft compliance report meeting is the moment Oracle transitions the engagement from LMS to its commercial sales team. Oracle's message: the audit found this gap, and here is the products/subscription package that will resolve it. The package is invariably positioned at or above list price, justified by the audit findings, and accompanied by timeline pressure — "we need to resolve this by end of quarter."
You are not obligated to accept Oracle's compliance report or their remediation proposal without challenge. The draft report is Oracle's interpretation of the data — it is not a legal finding. You have the right to dispute specific line items, challenge the calculation methodology, and propose alternative remediation approaches. This is the stage at which independent Oracle licensing expertise creates the most immediate financial value — every line item challenged and reduced before settlement is a permanent saving.
Our audit defence team challenges Oracle's compliance reports line by line — Core Factor calculations, cluster scope, option attribution, and entitlement mapping. The average Oracle audit claim is 3–5× what the customer actually owes after independent challenge.
Settlement negotiation is Oracle's sales process operating under the leverage created by the audit claim. Oracle's negotiating position: the compliance gap represents Oracle's entitlement, and resolution requires purchasing the identified shortfall. Oracle typically offers time-limited discounts — "we can offer 40% if you resolve this by end of month" — creating urgency that compresses your negotiating window and limits your ability to build a counter-position.
Effective settlement negotiation requires an independent counter-analysis of Oracle's compliance report, clear documentation of the challenges to Oracle's methodology, a benchmark of what comparable organisations have paid to settle similar claims, and understanding of Oracle's commercial priorities at the time of negotiation — which product lines Oracle is pushing, which customers Oracle needs to close for revenue targets, and whether a restructured deal serves Oracle's interests as well as yours.
Oracle audits rarely end with the customer paying Oracle's initial claim figure. The gap between initial claim and final settlement is typically 40–70% when the customer is represented by experienced, independent Oracle licensing advisors. However, achieving this requires entering settlement with a credible counter-position, not merely pushing back emotionally on Oracle's number.
Read our Fortune 500 Bank EA Restructure case study for a detailed example of audit-driven settlement negotiation that saved $8M against Oracle's initial claim position.
The most important principle in Oracle audit defence is to engage independent expertise before responding to Oracle at any stage. The following priority actions apply at each point in the process.
A 42-page tactical manual covering every stage of the LMS audit process — scripts decoded, response frameworks, Core Factor challenge methodology, option attribution disputes, and the complete settlement negotiation playbook. Written by former Oracle LMS consultants.
Download Free →Weekly briefings on Oracle audit trends, LMS methodology updates, script changes, and settlement benchmarks. Free. Read by ITAM leads, CIOs, and legal teams at global enterprises.
No spam. Unsubscribe anytime. Not affiliated with Oracle Corporation.
We manage Oracle audits from notification through settlement. Former Oracle LMS consultants with complete insider knowledge of Oracle's claim methodology, script analysis, and settlement strategy — working exclusively for the buyer.
✓ Confidential · ✓ Independent · ✓ Not affiliated with Oracle Corporation
Free Research
Download our Oracle SaaS Subscription Negotiation Guide — expert analysis from former Oracle insiders, 100% buyer-side.
Download the SaaS Negotiation Guide →