Negotiating Options Findings Down

Why is an options finding an opening position, not a bill?

An options finding is an opening position because the preliminary report arrives inflated at list price and assumes full, deliberate reliance on every flagged option across the estate. Oracle prices a usage flag as if you bought the option for every database it touched, at the published rate, with no discount. That is a negotiating opening, not a settled liability, and treating it as a bill concedes the whole gap before the conversation starts.

The reframe is the first buyer move. An options finding reflects what a script saw, which is that a feature registered as used, not that you depended on it or chose it. The number is large because it is built from list prices and worst case assumptions, both of which are negotiable. Understanding the finding as an opening bid is the foundation, and the wider options mechanics sit in the Oracle database licensing guide.

How do you separate genuine reliance from incidental flags?

You separate genuine reliance from incidental flags by reading the feature usage data for each option, so a feature used continuously in production is treated differently from one touched once during a past administrative session. Genuine reliance shows as sustained, recent, repeated usage tied to a workload. An incidental flag shows as a single use, an old isolated date, or a pattern that matches a one off action rather than a dependency. The distinction is evidentiary, and it decides how much of the finding stands.

This is the core of every options dispute. Where an option was genuinely never relied upon, the case to remove it entirely is set out in disputing options enabled but never used. Where it was used incidentally and stopped, the case is to price the brief use, not perpetual reliance. The evidence comes from your own data, read carefully, which is why detecting usage early matters so much, as covered in detecting accidentally enabled options.

Should you disable an option before negotiating?

You should usually disable an option you do not need before negotiating, with a documented date, because doing so demonstrates the usage was not a deliberate reliance and stops the clock on any further use. Disabling is a clear, datable action that supports the incidental argument and removes the risk of the usage continuing while the negotiation runs. It also signals good faith, that you are resolving the position rather than defending continued unlicensed use.

Disablement is not an admission. It is housekeeping that strengthens the case to negotiate the finding down rather than license the option in perpetuity. Where an option turns out to be genuinely useful, the alternative is to license it deliberately on planned terms, which is a far better outcome than buying it under audit pressure at list price. Either way the decision is yours, made from your own data, before the negotiation concludes.

Why negotiate the remediation rather than the list price?

You negotiate the remediation rather than the list price because the list price is a starting figure built from Oracle's worst case assumptions, while the remediation is the commercial resolution of what you genuinely need going forward. The conversation that matters is not how large the opening number is, but what you will actually license, on what metric, at what discount, and with what protection against the same finding recurring. That conversation is grounded in your real position, not the inflated opening.

Framed this way, an options finding becomes a normal commercial negotiation. You bring evidence of genuine reliance, you have disabled what you do not need, and you discuss the forward licensing of what remains at a negotiated rate. This keeps the resolution proportionate and forward looking, and it is the same discipline that governs any Oracle settlement, described in negotiating the remediation, not the list price, across our negotiation guidance.

A worked example

Consider an anonymized logistics firm whose audit flagged Tuning Pack and Partitioning across fifteen databases. The opening finding priced both options on every one at list price.

Tuning Pack proved incidental on most databases and was disabled with documented dates, while Partitioning was genuinely relied upon on three. The firm licensed Partitioning on those three at a negotiated rate and removed the rest, cutting the defended position by roughly 76 percent, within the 60 to 80 percent range a line by line review typically achieves. This example is illustrative and anonymized, and outcomes depend on your estate, your contract and your evidence.

Your next step

An options finding is one of the most negotiable claims Oracle issues, but only if you bring evidence and treat the opening number as a position. A buyer side review separates reliance from noise and negotiates the remediation on your behalf. Our advisors work on a Fixed Fee or Gainshare basis with no risk to you, and we reduce your Oracle exposure or we reimburse our service fee.