An Oracle audit letter usually lands at a bad time, and the clock starts when it does. Most of the exposure isn't fraud. It comes from features that run by default, virtualization rules that live outside your contract, and a Java price list built on headcount. Here's what tends to trigger a review, where the findings usually come from, and what to do before the letter arrives.

The short answer

  • Common triggers, according to licensing advisors, include M&A activity, Java downloads tied to your company, lapsed or shrinking support, and infrastructure changes.
  • The biggest exposure areas are usually database options and packs, VMware and other virtualized environments, and Java SE.
  • Prepare now: reconcile entitlements against deployments, control which features can be switched on, and get specialist licensing counsel involved before you answer Oracle.

What an Oracle audit actually is

Oracle's License Management Services team describes its job as performing "objective software license reviews" of customers to ensure contractual compliance, separately from sales. Whatever it's called, a review or an audit, your rights and obligations come from your contract, not from the tone of the email.

Read your own audit clause. Insight, a reseller with an Oracle licensing practice, quotes the standard wording: Oracle may audit on 45 days' written notice, you agree to cooperate, including running Oracle's data measurement tools, and you have 30 days from written notification to remedy any non-compliance. Older versions said 30 days to pay. Your version, and anything negotiated into it, is what counts.

This article isn't legal advice. Audit clauses, policy documents, and settlement terms are legal questions, and specialist Oracle licensing counsel is worth involving early.

How the standard Oracle audit clause runsAs quoted by Insight. Your contract version, and anything negotiated into it, is what counts
  1. 1Written notice

    Oracle notifies you that it will review your licenses.

  2. 245 daysNotice period

    Time to prepare before the audit begins.

  3. 3Audit

    You cooperate, including running Oracle's data measurement tools.

  4. 4Findings

    Oracle reports any non-compliance in writing.

  5. 530 daysTo remedy

    Time to resolve non-compliance from written notification.

Source: Insight. This isn't legal advice.

What tends to trigger a review

Oracle doesn't publish its selection criteria. Licensing advisors describe consistent patterns, though. Redress Compliance, which sells Oracle audit defense, lists these signals:

  • Java downloads associated with your corporate domain, and support-portal activity on lapsed entitlements.
  • Corporate events: acquisitions, divestitures, rapid growth, and large outsourcing deals.
  • A lapsed or shrinking support line with nothing replacing it.
  • Questionnaires, answered or ignored, and earlier audit history.

Add infrastructure change to the list. A lawyer who represents clients in Oracle audits advises assessing the licensing impact before you change virtualization, clustering, or partitioning, because some of the rules sit outside the license documents.

Where the exposure usually sits

Database options and packs

Oracle Database Enterprise Edition ships with management packs that are separately licensed. According to Oracle's own reference documentation, the parameter that controls access to the Diagnostics and Tuning Packs defaults to DIAGNOSTIC+TUNING on Enterprise Edition. The licensing manual says any method of accessing Diagnostics Pack functionality, including direct access to the underlying data, requires a license. A DBA pulling a performance report on an unlicensed database can create usage you'll be asked to explain.

Virtualization

Oracle's Partitioning Policy classifies VMware as soft partitioning, which it says is not permitted as a way to limit the licenses required. It lists the hard-partitioning technologies it does accept. Oracle Linux KVM and Oracle VM qualify only when configured as Oracle specifies. The same document says it's "for educational purposes only" and "does not constitute a contract." How much weight it carries against your agreement is exactly the kind of question to put to counsel, not to settle on a call with Oracle.

Java SE

Oracle's Java SE Universal Subscription price list (dated October 8, 2026) counts Employees, not installations. That means all your full-time, part-time, and temporary staff, plus those of contractors, outsourcers, and consultants who support your internal operations, whether or not they use Java. The price list's own example: 3,000 employees at $10.50 a month comes to $378,000 a year. Below 3,000 employees, flat bands apply. The band for 101 to 500 employees is $10,000 a year, and each additional employee up to 2,999 adds $147.20 a year.

Oracle's JDK FAQ says Oracle JDK 25 and later is free for all users under its No-Fee Terms. Updates to older releases (8, 11, 17, and 21) come under the OTN license, which is free only for personal, development, and certain other uses. Open-source OpenJDK builds are another option. Knowing which Java you run, where, and under which license is most of the work.

What auditors typically ask for

Expect a kickoff call, then requests for deployment data: server and cluster details, virtualization configuration, database feature usage, application user lists, and output from Oracle's measurement scripts. The Scott & Scott article recommends two things. Have your systems and security teams review Oracle's scripts before you run them. And negotiate the scope, such as which entities, regions, and environments are in play, before data changes hands.

A preparation checklist you can start this quarter

  1. Assemble your entitlements. Master agreement, every ordering document, and the policies they reference. Start with recent support renewals and work back.
  2. Inventory deployments the way Oracle would. Every server, cluster, and virtual host where Oracle software is installed or could run. Repeat it at least twice a year.
  3. Lock down packs and options. Where you don't own the Diagnostics or Tuning Packs, set the access parameter to NONE and record when you did it.
  4. Map virtualization boundaries. Document which hosts and clusters can run Oracle workloads, and why.
  5. Run a Java census. Count installations by distribution and version, and know your Employee number under Oracle's definition.
  6. Decommission what you don't use before any notice arrives, and keep the evidence.
  7. Name one point of contact and pick specialist licensing counsel in advance.

What not to do

  • Don't ignore the letter, and don't reply in detail before you've read your audit clause.
  • Don't send raw data unreviewed. Check every output for accuracy and scope first.
  • Don't let scope drift beyond what your contract allows.
  • Don't rush into a purchase to make findings go away. Any settlement should state exactly what it resolves. The Scott & Scott article stresses getting a full release of claims as of the resolution date.
  • Don't make changes mid-audit without advice. Uninstalling software after notice can complicate the record.

The longer-term fix is to have less to audit. Every workflow you move off Oracle is one less metric to count and defend. We offer that work, so weigh our view accordingly. But the arithmetic is yours to check: put your support bill and audit risk next to what it would cost to own the software outright.

Five questions to answer before Oracle asks them

  1. Which version of the audit clause are we on, and what did we negotiate?
  2. Which databases are on Enterprise Edition, and is pack access set to match what we own?
  3. Which hosts could run Oracle workloads under Oracle's partitioning rules, not just the ones that do?
  4. What is our Employee count under Oracle's Java definition, including contractors?
  5. Who speaks for us, and which licensing counsel will we call?

Where to go from here

Start by reconciling what you own against what you run, then put a number on what staying costs. If you want a second opinion, tell us what you run and what you pay. We'll be honest about whether moving off Oracle makes sense. You can also see how a staged approach works on our Escape Oracle page.

Sources