If you read nothing else
Oracle accidental option usage is the inadvertent activation of a separately licensed Database option or management pack — Diagnostics Pack, Tuning Pack, Partitioning, Advanced Compression — through ordinary administrative work, with no purchase order and no warning. Oracle's feature-usage views record it for up to 1,500 days, and an audit prices each one at full list plus back-support. Find it first, switch it off, document the remediation, and never hand Oracle raw usage logs.
This white paper covers Oracle accidental option usage end to end: which options auto-enable, how Oracle detects them, what they cost in a 2026 audit, and the remediation and challenge sequence that keeps a click in Enterprise Manager from becoming a six-figure claim. Every price and policy figure carries a source and a date.
Key takeaways
- The options are not free — only the install is. Diagnostics Pack ($7,500/processor), Tuning Pack ($5,000/processor), Partitioning ($11,500/processor), and Advanced Compression ($11,500/processor) ship inside Enterprise Edition but are separately licensed; using one without entitlement is a compliance gap (Oracle Technology Price List, April 2026).
- Diagnostics Pack is the most common accidental finding. It enables by default on Enterprise Edition, and hourly AWR snapshots plus a single click on the Enterprise Manager performance page all register as usage — it is inadvertently active in roughly 40% of enterprise Oracle estates (Oracle Licensing Experts engagement data, 2026).
- Oracle reads up to 1,500 days of usage history. The
DBA_FEATURE_USAGE_STATISTICSview records option and pack usage, refreshes weekly, and Oracle's scripts mine it for any non-zero entry across roughly the prior four years (Oracle-Base; My Oracle Support Doc ID 1317265.1, 2026). - Back-support multiplies the bill. An accidental-usage claim is priced at list plus support arrears on the alleged shortfall, on top of new licenses at 22% of net license value per year (Oracle Software Technical Support Policies, 2026); the arrears frequently exceed the license cost itself.
- Most claims are recoverable, not payable. Across 600+ engagements, accidental option and pack usage surfaces in roughly four of five Enterprise Edition estates we review, and most of the resulting exposure is removed by remediation, evidence, and product substitution rather than purchase (Oracle Licensing Experts benchmark, 2026).
Recommendations by role
Accidental option usage is created by engineers and paid for by finance. Here is what each owner must do to contain it.
SAM / ITAM Manager
- Run the options-and-packs usage query against every Enterprise Edition database now — on your own clock, not a 45-day audit clock.
- Reconcile each non-zero feature against entitlement, and flag Diagnostics Pack, Tuning Pack, and Partitioning as the priority three.
- Maintain a dated remediation log so any switched-off option has a defensible end date if Oracle ever asks.
Head of Infrastructure / DBA Lead
- Disable the management packs at the instance level (
CONTROL_MANAGEMENT_PACK_ACCESS) on every database that is not licensed for them. - Turn off the default automatic SQL tuning task and review AWR retention so routine jobs stop generating pack usage.
- Block any Oracle-supplied script from running or returning output without review by the single licensing owner.
CFO / Finance
- Model worst-case exposure as list price plus back-support, so any settlement target is set by you, not by Oracle's letter.
- Treat an option finding as a negotiation input to the next renewal, never as a standalone invoice to be paid on receipt.
- Fund a quiet self-audit now; it is an order of magnitude cheaper than discovering the same usage under a live review.
VP Procurement / Vendor Management
- Demand the underlying feature-usage evidence and dates behind every option line Oracle claims.
- Push back on retroactive back-support; it is the most negotiable element of any accidental-usage claim.
- Fold any genuine, evidenced gap into a discounted forward agreement rather than a one-time true-up at list.
The accidental option usage framework: how a click becomes a claim
Each question below is one a DBA lead, SAM manager, or CFO actually asks once an option finding surfaces. Lead with the answer; the move follows.
What counts as accidental Oracle option usage?
Accidental option usage is any activation of a separately licensed Database option or management pack that happens without a purchase order, through normal administrative work rather than a deliberate deployment decision. An option is a chargeable Database feature — Partitioning, RAC, Advanced Compression — that installs with Enterprise Edition but must be licensed before use. A management pack is a chargeable monitoring or tuning bundle — Diagnostics Pack, Tuning Pack — in the same posi
Audit tactics, negotiation leverage and licensing traps — decoded by former Oracle insiders. Join 2,000+ buyers. No spam, unsubscribe anytime. Independent of Oracle Corporation. Not affiliated with Oracle.Get the weekly briefing Oracle hopes you never read