Oracle Database options & management packs: the Diagnostics/Tuning Pack licensing risk (2026)

Oracle Database options and management packs are licensed separately from the database itself, and using one you haven’t licensed is consistently the single largest source of findings in an Oracle review — by most accounts, more than four in five reviewed estates turn up at least one. The reason is simple: a pack can switch on without anyone deciding to use it.

How a pack switches on by accident

• Diagnostics Pack is triggered by AWR, ADDM, and parts of Enterprise Manager — features a DBA may open without realizing they’re licensed.
• Tuning Pack is triggered by the SQL Tuning Advisor.
• Partitioning is triggered the moment a partitioned table exists.
• Advanced Compression, Advanced Security, and others follow the same pattern: a feature gets used, and the meter starts.

Oracle records this in the database’s own feature-usage history, which is exactly what a review examines. If the option was in use and you weren’t licensed for it, that’s a gap — regardless of intent.

Why it stays invisible until the review

Entitlements are checked occasionally; feature usage changes continuously. A patch that enables a feature by default, or a one-off action by a DBA, can start a pack months before anyone looks. By the time a review runs, the usage is already on the record.

Seeing what’s actually in use

The defensible position is accuracy: know which options are genuinely in use, then license what you need or stop using what you don’t. RenewalIntel reconciles the options in use across your estate against what you’re licensed for and flags each unlicensed option in use — so you can close the gap deliberately, before a review does it for you. (It surfaces which options are in use; it does not price each option individually, and it is not audit or legal advice.)