What LMS actually does.
Oracle License Management Services is the internal Oracle function that runs license audits. The function reports through Oracle's commercial organisation, not through an independent compliance group. The audit is a tool that Oracle uses to identify deployment beyond entitlement and to convert that gap into new commercial revenue. The audit is not a neutral process. The findings are commercial inputs to a sales negotiation that follows the audit closing meeting. The buyer side response treats the audit as a structured commercial process and defends accordingly.
The notification phase.
The audit begins with a formal notification letter. The letter cites the audit clause in the customer's Oracle Master Agreement or Oracle Software License and Services Agreement, identifies the LMS lead, and proposes a kick off date. The notification is the buyer side's first decision point. The decision is not whether to engage but how. The first response to the notification sets the tone for the entire audit. The buyer side response acknowledges the audit, requests a defined scope, requests the audit methodology in writing, and proposes a kick off date that allows the buyer side to prepare. We cover the first response in detail in our first 48 hours guide.
The kick off meeting.
The kick off meeting is the formal start of the audit. LMS presents the audit scope, methodology, timeline, and data request. The buyer side response at kick off includes a formal scope acknowledgement, a documented methodology review, a timeline counter proposal that includes buyer side review windows, and a defined single point of contact for all audit communication. The kick off meeting is not a working session. It is a scoping meeting. No deployment data is shared at kick off. The buyer side discipline is to keep the kick off short, structured, and documented.
The data collection phase.
The data collection phase is the longest phase of the audit. LMS requests deployment data using a defined data request template. The template is broad. The template typically asks for every server hosting Oracle software, every named user with access to Oracle software, every cloud deployment of Oracle software, and every virtualisation host running Oracle software. The buyer side response is to scope the data request to the audit scope. Data outside the audit scope is not shared. The data request template is treated as a starting point for negotiation, not as a fixed list.
LMS audit phases
- Notification letter and engagement of the buyer side single point of contact.
- Kick off meeting with scope, methodology, and timeline agreement.
- Data collection under a scoped data request.
- Oracle script execution and output review.
- Preliminary findings letter and buyer side response.
- Closing meeting with negotiated findings.
- Commercial settlement and contract documentation.
The script execution.
The script execution phase runs Oracle's discovery scripts in the customer environment. The scripts are provided by LMS and run by the customer. The script output is shared with LMS. The buyer side discipline is to run the scripts in a controlled environment, to review the output before sharing, and to document any environmental factors that may produce misleading output. The scripts are not always correct. The scripts do not always reflect the contract definition of licensable use. The buyer side review of script output is the single most valuable defensive activity in the audit. We cover the script review process in our database audit explainer.
The preliminary findings.
The preliminary findings letter is the LMS statement of the gap between deployment and entitlement. The letter quantifies the gap in license units and translates the license unit gap into a dollar amount at Oracle's list price. The list price translation is not the settlement amount. The list price translation is the opening position for the commercial negotiation that follows. The buyer side response to the preliminary findings letter is a detailed technical and contractual response that contests every finding that can be contested. The response is documented in writing and is the foundation for the commercial negotiation. We cover the findings response in our findings negotiation explainer.
The closing meeting.
The closing meeting is the formal end of the audit. LMS presents the final findings. The buyer side presents the response. The findings are reconciled. The audit closing is documented in a closing letter. The closing letter is the basis for the commercial negotiation that follows. The buyer side discipline at closing is to ensure that the closing letter reflects only the agreed findings and that disputed findings are documented as disputed. A closing letter that records disputed findings as agreed is a commercial liability that follows the customer into the post audit period.
The commercial settlement.
The commercial settlement is the negotiation of the resolution of the audit findings. The settlement may take the form of a license purchase, a support stream extension, a cloud commitment, a contract restructuring, or a combination. The buyer side discipline is to evaluate every settlement option against the customer's Oracle roadmap and to select the settlement that best serves the customer's commercial interests. The audit settlement is often the catalyst for a broader Oracle deal restructuring. The audit closure can be paired with a renewal, a ULA, or a cloud migration on terms that are favourable to the buyer side.
Related resources.
- Audit Defense pillar guide
- Audit Defense service
- ULA deal type page
- Oracle Database product page
- Oracle Audit Defense Handbook 52 page reference paper.
- Oracle Audit Findings Negotiation related sub article.
- Oracle Audit Counter Claim Strategy related sub article.