What do Oracle auditors request?
Oracle auditors request five things in most engagements: collection script output, a server and processor inventory, the virtualization topology, feature usage data, and your contracts. Each item exists to build one side of a comparison. Oracle wants a measured picture of what you are running so it can set that against the entitlements you hold and turn any gap into a finding. Understanding what each request is for lets you supply accurate data without supplying Oracle the most aggressive possible reading of your estate.
Why does Oracle ask you to run its scripts?
Oracle asks you to run its scripts because the script output is the fastest way for Oracle to see usage you might not volunteer, including options enabled by accident. The measurement utilities read the database and the operating system and report processor counts, edition, enabled options and management pack usage. The catch is that the output is generated on Oracle's terms and reported in Oracle's format, and it can overcount across virtualization layers. Running and submitting those scripts is a decision, not an obligation, and the raw output should be reviewed and reconciled first. The mechanics are covered in how an Oracle audit actually begins.
Treat script output as a draft, not a disclosure. Reconcile every host and every reported option against what is genuinely deployed and operationally used before anything is submitted.
Why the server and processor inventory matters
The server and processor inventory matters because it sets the core count that drives Processor licensing, and the core count is then multiplied by the core factor. A wrong processor type, an outdated server list or a failure to apply the correct factor can double the apparent license requirement. Oracle benefits when the inventory is read generously in its favour. You benefit from confirming the processor type, applying the current core factor table accurately, and excluding hardware that is decommissioned or out of scope. The detail sits in the Oracle Database Licensing Guide.
Why auditors want the virtualization topology
Auditors want the virtualization topology because it is the basis for the cluster wide claim, Oracle's assertion that you must license every core a workload could reach. A full map of hosts, clusters and shared storage lets Oracle draw the largest possible boundary. Under Oracle's partitioning policy, which does not recognise VMware, Hyper V or KVM as hard partitioning, a single licensed virtual machine can be used to pull an entire cluster into scope. That claim rests on policy rather than your signed contract, and the contract governs where the two disagree. The defense is set out in the Oracle Virtualization Licensing Guide.
Why feature usage data is requested
Feature usage data is requested because it reveals options and management packs that were enabled, sometimes by a single administrative click, and each one is separately licensable. Many options install by default, and opening the wrong screen in Enterprise Manager can register usage of the Diagnostics or Tuning Pack. The usage data Oracle reads does not distinguish a deliberate, operationally meaningful use from an accidental one, so it falls to you to dispute usage that was never genuine. This is one of the most common sources of unexpected liability in any audit.
| Request | What it drives | Where it overcounts |
|---|---|---|
| Script output | The whole measured picture | Sweeps every visible host |
| Processor inventory | Processor license count | Wrong type or factor |
| Virtualization topology | The cluster wide claim | Largest possible boundary |
| Feature usage data | Options and packs liability | Accidental, default usage |
| Contracts | Your entitlements | Policy read over contract |
Why Oracle asks for your contracts
Oracle asks for your contracts to establish entitlements, but the contract is also your strongest asset, because the signed Oracle Master Agreement beats Oracle's policy documents whenever the two disagree. Read your own agreement before you hand it over and know what it actually says about partitioning, metrics and audit cooperation. Often the contract is narrower and more favourable than the policy interpretation Oracle applies on top of it. Holding the contract above the policy paper is the move that dismantles inflated claims.
Why a reviewed data set changes the outcome
A reviewed data set changes the outcome because it removes the overcounts before they become a finding, and independent line by line review of findings typically cuts claims 60 to 80 percent. The preliminary number arrives inflated and priced at list because the audit is a negotiation dressed up as an inspection, and roughly 20 to 30 percent of Oracle's on premises license revenue is estimated to come from audits. Submitting accurate, reconciled data is not obstruction, it is the difference between defending a true position and accepting an inflated one. When the number is large or the deadline is close, an independent buyer side review carries the work the rest of the way. See also the Oracle audit myths that cost money.
Talk through a live data request with a buyer side analyst before you respond. Book a strategy call and bring the auditor's checklist.