The options evidence argument is the buyer side case that a usage flag is a measurement artefact rather than a deployment, supported by evidence the feature was never used in production and was disabled on discovery, which is part of why independent review typically cuts claims 60 to 80 percent.
What is the options evidence argument?
The options evidence argument is the structured buyer side case that an option usage flag does not, by itself, prove a licensable deployment. Oracle audits run through GLAS, and a finding will list any flagged option as used and price it at list. The evidence argument answers that line directly: it shows what the flag actually represents, when it occurred, whether production ever relied on the feature, and what was done on discovery. Built well, it converts an inflated options line into a measurement question that the contract can resolve in the buyer's favour.
What evidence challenges an option finding?
The evidence that challenges an option finding is the usage history, the timing and isolation of any flag, the change records around it, and proof the feature was disabled. Feature usage data shows whether an option ran once or ran continuously in production. The timing shows whether a flag coincided with a one off action such as an advisor run. Change records tie the flag to a specific event rather than an ongoing reliance. Together these turn an assertion of usage into a documented, dated, isolated event that can be argued against the contract.
Why a flag is not a deployment
A flag is not a deployment because the database records that a feature was exercised, not that the business depends on it. Many options install by default, and a single Enterprise Manager click can flag Diagnostics or Tuning as used. The distinction the evidence argument draws is between an accidental, isolated exercise of a feature and a genuine production deployment that the workload relies on. A finding collapses that distinction, treating every flag as a deployment. The evidence pack restores it, line by line.
| Evidence | What it shows |
|---|---|
| Feature usage history | Whether the option ran once or continuously |
| Flag date and context | Whether usage was isolated or ongoing |
| Change and incident records | The specific action behind the flag |
| Disable confirmation | That the feature is no longer in use |
Does disabling the option remove exposure?
Disabling the option is part of the argument rather than the whole of it. On its own, disabling shows the feature is no longer in use, which is necessary but not sufficient. Combined with evidence that production never relied on the feature, disabling supports the case that the original flag was an artefact and that no licensable deployment ever existed. The order matters: gather the usage evidence first, then disable, and record both, so the timeline reads as a managed correction rather than an admission.
How to build the evidence pack
You build the evidence pack by collecting feature usage data, mapping each flagged option to the action that caused it, documenting the production reliance test, and recording the disable step with dates. Present it line by line, one option at a time, with the contract terms that govern usage alongside. This is the same discipline that underlies independent review generally, and it is why a careful line by line review of options findings typically removes a large share of the preliminary number rather than negotiating a discount on it.
A worked example
Consider an anonymized insurance firm whose finding listed Diagnostics and Tuning packs across a dozen databases. The evidence pack showed the flags traced to a single performance review exercise, with no production reliance, and the features had been disabled. Presented option by option against the contract, the pack lines were withdrawn and the exposure fell sharply from the opening figure. No client names, sector level example only.
The buyer moves
The buyer moves are to collect feature usage history, tie each flag to its cause, run the production reliance test, disable unlicensed features, and present the evidence option by option against the contract. Done in order, these moves give an inflated options finding nowhere to stand and turn the conversation from list price to measurement.
Where to go next
This piece links up to the Oracle Database Licensing Guide. Keep reading across the cluster:
To build the evidence pack for your own options finding, book a strategy call or read the Oracle Database Licensing Guide.