The Oracle Diagnostic Pack and its companion the Tuning Pack are database management options that attach to Oracle Database Enterprise Edition. They are licensed separately, priced per processor or per named user, and they carry some of the highest margins in Oracle's database catalogue. For buyers they are also one of the most common sources of overspend, because the packs are often quoted as a bundle, deployed without conscious selection, and renewed year after year without anyone asking whether they are needed. This article sets out how to price and right size the management packs from the buyer side.
This article is a companion to our database negotiation pillar and supports our contract review service.
What the Diagnostic Pack Actually Covers
The Diagnostic Pack licenses a set of features built into Oracle Database Enterprise Edition, including the Automatic Workload Repository, the Automatic Database Diagnostic Monitor, and the performance pages of Enterprise Manager. The Tuning Pack adds the SQL Tuning Advisor and related features. The important point for buyers is that these features ship inside the database binary. They are not separate software. They are switches that Oracle has chosen to license as paid options.
Because the features are present by default, it is very easy to use them without realising they require a licence. A database administrator who runs an AWR report or opens the performance page in Enterprise Manager has used the Diagnostic Pack, whether or not the organisation has paid for it. This is the trap. The packs generate licence exposure through ordinary administrative work, which is exactly why they appear so often in Oracle audit findings.
Why the Packs Inflate Deals
The management packs inflate database deals in two ways. The first is at purchase, where Oracle quotes the packs alongside the database licence as if they were a standard component. A buyer who accepts the quote pays for packs across the entire database estate, including databases that will never use the features. The second is at renewal, where the packs sit in the support base and compound the support fee year after year, as described in our term versus perpetual analysis.
The single most common database overspend we find is management packs licensed across the full processor count when only a handful of databases ever use them. The packs are quoted as a default, accepted without scrutiny, and then carried in the support base for a decade. Right sizing them at the point of negotiation often returns more than any discount on the database itself.
The Right Sizing Question
The disciplined approach starts with a simple question. Which databases actually use the Diagnostic and Tuning Pack features, and which do not? Most estates have a small number of performance critical databases where the packs deliver real value, and a long tail of databases where they are never touched. Licensing the packs across the whole estate to cover the few that use them is the most expensive way to solve the problem.
The right sizing exercise produces a defensible position. The organisation licenses the packs on the databases that need them, disables the features on the databases that do not, and documents the configuration. This both reduces the licence requirement and creates the evidence needed to defend the position in an audit. Our Oracle Database product page covers the option model in more detail.
Disabling the Packs Cleanly
Disabling the management packs is a configuration step, not an uninstall. The CONTROL_MANAGEMENT_PACK_ACCESS parameter governs access to the Diagnostic and Tuning Pack features. Setting it to NONE blocks the features and removes the licence requirement, provided the configuration is genuinely enforced and the features are not accessed by other means such as Enterprise Manager. The disabling must be complete and documented to hold up under scrutiny.
The common mistake is to disable the parameter on the database but continue to use Enterprise Manager pages that draw on the packs. The licence requirement follows usage, not the parameter setting alone. A clean disable means the parameter is set, the Enterprise Manager configuration is aligned, and the administrators understand which tools they may use. Anything less leaves residual exposure.
Pricing the Packs in a Negotiation
When the packs are genuinely needed, they should be priced as part of the overall database negotiation rather than accepted at list. The packs carry list prices that are a meaningful fraction of the database licence, and they attract the same discount levels as the database itself when negotiated together. A buyer who negotiates the database hard but accepts the packs at list has left money on the table. The packs belong in the same discount conversation.
The tactic is to bundle the packs into the total deal value and negotiate the blended discount, rather than letting Oracle hold the packs at a higher margin. Because the packs are pure margin for Oracle, there is room to move on them, particularly at period end. Timing the negotiation to Oracle's fiscal calendar, as covered in our GoldenGate pricing article, applies equally to the management packs. Our renewal negotiation service handles this blended approach.
The Audit Dimension
The management packs are a favourite of Oracle audit teams precisely because the features are used so easily without a licence. An audit script will detect AWR snapshots, SQL Tuning Advisor runs, and Enterprise Manager pack usage, and any of these on an unlicensed database produces a finding. Buyers who have not right sized the packs often discover their first real exposure during an audit, when the leverage has already shifted to Oracle.
The defensive posture is to address the packs before an audit, not during one. An organisation that has inventoried pack usage, licensed where needed, and disabled where not, walks into an audit with a defensible position. An organisation that has ignored the packs is exposed on every database where an administrator ever ran a report. For the broader audit framework, the Oracle Negotiation Playbook sets out the methodology, and our database licensing deal page covers the contract structure.
Where to Read Next
For the GoldenGate option see our GoldenGate pricing article. For the licensing model decision see our term versus perpetual analysis. For the full database strategy see our database negotiation pillar. The Oracle Negotiation Playbook covers the complete methodology.