Last updated: June 2026
Oracle Database ships with options and management packs that switch themselves on the moment a DBA runs a routine command, builds an index, or opens a tuning screen. You never bought them. You never meant to use them. But Oracle's scripts recorded every event — and at audit time, each one becomes a back-licence claim. This white paper shows you exactly which features detonate, how Oracle proves usage, and how to shut the exposure down before an auditor ever asks.
Why this matters now: Oracle's own feature-tracking view, DBA_FEATURE_USAGE_STATISTICS, records option use whether or not you ever licensed it — and it cannot be retroactively cleaned without leaving a trail. A single accidental Partitioning, Diagnostics Pack, or Tuning Pack flag on a multi-core Enterprise Edition server can generate a six- or seven-figure claim. The time to find these is before Oracle's script does, not after.
"A DBA who opens the Performance or AWR pages in Oracle Enterprise Manager has, in Oracle's view, used the Diagnostics Pack — a separately licensed option. No purchase, no warning, no confirmation dialog. The console simply works, the feature flag is set, and the usage is logged. At audit, Oracle does not ask whether you meant to use it. They ask how many cores the database runs on, and they multiply."
"Partitioning is the option enterprises most often deploy without realising it costs extra. A developer partitions one large table for performance, or a vendor's schema ships partitioned objects, and Enterprise Edition cheerfully creates them. The feature is licensed per processor across the entire database — not per partitioned table. One accidental partition exposes every core on the server."
"DBAs who discover accidental usage often want to reset the feature-usage history. Oracle's view retains historical samples, and a sudden gap is itself a flag. The defensible path is not erasure — it is documented remediation: disable the feature, record the date and reason, and build a contemporaneous evidence file showing the use was incidental and has stopped. That file is what protects you when Oracle disputes the timeline."
34 pages. Immediate access. No spam — only relevant Oracle licensing intelligence from our advisory team.
Our Audit Defense team runs an independent, forensic review of your feature-usage data, identifies accidental option and pack exposure, and builds the contemporaneous evidence file that lets you remediate defensibly. Start with our Oracle Database Licensing Guide or review a client case study.