What are Diagnostics Pack and Tuning Pack?
Diagnostics Pack and Tuning Pack are two separately licensed management packs that layer on top of Oracle Enterprise Edition, with Diagnostics Pack covering performance monitoring and diagnosis and Tuning Pack covering automated tuning advisors. They are not part of the base database license. They are extra entitlements bought on top, and they are among the most valuable items in Oracle's option catalogue. They are also among the easiest to use without meaning to, which is the combination that makes them the first place an audit looks.
The packs deliver genuinely useful capability. The Automatic Workload Repository, the Automatic Database Diagnostic Monitor, the active session history, and the tuning advisors are tools database administrators reach for naturally. That usefulness is precisely the trap: the features are reached through ordinary administrative work, so usage accrues in the normal course of running the database, and the usage is recorded whether or not anyone made a licensing decision.
What triggers Diagnostics Pack and Tuning Pack usage?
Diagnostics Pack usage is triggered by using the Automatic Workload Repository, ADDM, active session history, or the performance pages of Enterprise Manager, and Tuning Pack usage is triggered by the automatic tuning advisors, so a single query or one screen can flag either pack as used. Querying an AWR view, generating an AWR report, or opening the performance tab records Diagnostics Pack. Running the SQL Tuning Advisor or accepting an automatic tuning recommendation records Tuning Pack. There is no prompt and no gate. The database does what it is asked and writes the usage to the feature usage views an auditor will read.
One AWR query or one click on a performance screen can record Diagnostics Pack. One run of the tuning advisor can record Tuning Pack. The usage view captures the action, not your intent, so control the action to control the exposure.
| Action | Pack recorded |
|---|---|
| Querying or reporting from AWR | Diagnostics Pack |
| Running ADDM or active session history | Diagnostics Pack |
| Opening the Enterprise Manager performance pages | Diagnostics Pack |
| Running the SQL Tuning Advisor | Tuning Pack |
| Accepting an automatic tuning recommendation | Tuning Pack |
Why do the two packs travel together in findings?
The two packs travel together because Tuning Pack generally requires Diagnostics Pack as a prerequisite, so a Tuning Pack usage record almost always sits alongside a Diagnostics Pack record. An audit that finds tuning advisor usage will therefore usually claim both packs across the same servers, doubling the apparent exposure on that hardware. This dependency is useful to understand on defence as well as on offence: if the Diagnostics Pack usage can be shown to be incidental or contract permitted, the Tuning Pack claim that rests on it weakens with it. The two stand or fall together more often than a preliminary report admits.
How do you dispute a Diagnostics Pack finding?
You dispute a Diagnostics Pack finding by reading the usage history, distinguishing genuine reliance from accidental or one time use, and answering each server against the contract rather than the policy paper. A flag that reflects a single AWR query during a one off investigation is not the same as a production dependency on continuous monitoring, and the contract, not the usage view, defines what is licensable. Preliminary findings arrive inflated at list price, and management packs are a favourite source of that inflation because the usage trail looks conclusive until examined. Independent line by line review typically cuts claims 60 to 80 percent, and pack findings are a major part of that. For the wider argument, read disputing options enabled but never used.
Our options and packs detection guide shows how to read pack usage and disable safely before an audit. We reduce your Oracle exposure or we reimburse our service fee, on a Fixed Fee or Gainshare basis with no risk to you.
What is the buyer move?
The buyer move is to monitor pack usage yourself, restrict access to the triggering features where you do not hold the licenses, and treat any pack finding as a documented dispute. Check the feature usage views regularly, set the management pack access parameter to limit what can be reached, and brief administrators on which screens and tools create exposure. Keep a record of what was restricted and when, so a finding meets prepared evidence. Where a claim has already arrived, work it server by server against the real usage and the contract. For the surrounding context, read Oracle options and packs, the audit goldmine and the Enterprise Manager click that costs millions, then work up to the Oracle database licensing guide.
FAQ
What triggers Diagnostics Pack usage? Using AWR, ADDM, active session history, or the Enterprise Manager performance pages. A single AWR query or one click can flag the pack as used.
What is the difference between the two packs? Diagnostics Pack covers monitoring and diagnosis, Tuning Pack covers tuning advisors. Tuning Pack generally requires Diagnostics Pack, so a Tuning Pack finding usually carries a Diagnostics Pack finding with it.
Can you dispute a pack finding? Yes. Accidental or incidental usage can be evidenced against the contract, and line by line review typically cuts preliminary claims 60 to 80 percent.