Is the Oracle preliminary report a bill?
No, the Oracle preliminary report is an opening position priced at list, not a final invoice, and it is the most expensive myth in the whole process. An Oracle audit is a negotiation dressed up as an inspection, and the first number you see is designed to anchor the conversation high. It arrives inflated because it counts everything at full list price, assumes the widest possible deployment boundary and rarely credits the entitlements you already hold. Buyers who read that number as a debt pay far more than they owe. An independent line by line review of audit findings typically reduces the claim by 60 to 80 percent, which only happens when you treat the report as the start of a negotiation rather than the end of one. The full method is in the Oracle Audit Defense Guide.
Do you have to run every Oracle script?
No, running Oracle's collection scripts is a decision rather than an automatic obligation, and treating it as compulsory is the second costly myth. The scripts gather feature usage and deployment data, and in virtualized estates they can overcount by counting the same workload across multiple layers. Submitting raw script output without review hands Oracle the highest possible number and removes your chance to challenge it. Review the output first, reconcile it against your contract and your actual deployment, and decide what is accurate before anything leaves your network.
Treat every data set as a draft until your own team has checked it. Reconcile script output against entitlements and the real deployment boundary, then submit only what is accurate. Nothing leaves the building unreviewed.
Does Oracle policy override your contract?
No, the signed Oracle Master Agreement governs, and the belief that policy documents carry the same weight is the third myth that costs money. Oracle's partitioning policy, the one that declines to recognise VMware, Hyper V or KVM as hard partitioning, is a policy paper, not a contract term. When a cluster wide claim rests on that policy, it is resting on ground that is often weaker than your signed agreement. Contract language beats policy, so the first question on any virtualization finding is what the contract actually says, not what the policy asserts.
| The myth | The reality | Buyer move |
|---|---|---|
| The report is a bill | It is an opening position at list | Review line by line |
| You must run every script | It is a decision, scripts overcount | Review before submitting |
| Policy equals contract | The signed agreement governs | Read the contract first |
| Silence ends the audit | The window is 30 to 45 days | Manage scope and timeline |
Does ignoring the letter make it go away?
No, ignoring the audit notice does not end it, because the audit clause in your Oracle Master Agreement gives Oracle a contractual right to proceed, usually with a 30 to 45 day response window. The window is negotiable on timeline and scope, but it does not disappear if you stay silent. The productive response is to acknowledge the notice, confirm the scope and run the engagement on terms you have helped set. For the mechanics of that first response, see what triggers an Oracle audit and what Oracle auditors request and why.
What should you do instead?
Replace each myth with the buyer move and the exposure falls. Know your true position before the letter arrives, review every data set before it leaves, read the contract before you accept any policy claim, and treat the preliminary number as the opening bid it is. If a finding has already landed and the number looks frightening, that is exactly the moment a buyer side review pays for itself. Bring us the report and we will tell you what it is actually worth.
Have a preliminary finding in hand? Get a Quote for a buyer side review, or read the full method in the Oracle Audit Defense Guide.