Oracle Tuning Pack is a paid option that is easy to use by accident. A single click in Enterprise Manager can trigger a license obligation. Read the dependency and the audit trap before the next true up.
Oracle Tuning Pack is a per processor or Named User Plus database option that depends on the Diagnostics Pack and is the most common accidental usage finding in an Oracle audit. The 2026 guide prices it and shows the defense.
Oracle Tuning Pack is not part of Enterprise Edition. It is a paid option that the database can use the moment a DBA touches the wrong screen.
That is what makes it dangerous. The cost is ordinary. The audit exposure from accidental use is what catches buyers.
Tuning Pack is licensed on the same metric as the database it sits on, either per processor or per Named User Plus. It is a percentage uplift on the database license.
If the database is licensed per processor, Tuning Pack is per processor. If it is Named User Plus, the pack follows. The counts must match.
Like every option, Tuning Pack carries annual support at the standard rate. The support stream, not the license, is the recurring cost.
Oracle lists the options on its Oracle Database technologies page, and the licensing rules sit in the Database Licensing Information manual. Read the manual, not the brochure.
Tuning Pack cannot be licensed alone. It requires the Diagnostics Pack, so the two are bought and counted together.
Tuning Pack and Diagnostics Pack at a glance
| Item | What it does | License basis | Audit note |
|---|---|---|---|
| Diagnostics Pack | Performance monitoring, AWR, ADDM | Per processor or NUP | Prerequisite for Tuning |
| Tuning Pack | SQL Tuning Advisor, SQL Access Advisor | Per processor or NUP | Requires Diagnostics |
| Control parameter | Disables pack access | CONTROL_MANAGEMENT_PACK_ACCESS | Set to NONE to cap |
| Usage evidence | DBA_FEATURE_USAGE_STATISTICS | Read by auditors | Records accidental use |
Because Tuning requires Diagnostics, a Tuning obligation always implies a Diagnostics obligation. Model both when you price exposure.
Automatic Workload Repository use signals Diagnostics Pack. Auditors read the feature usage views to reconstruct what ran.
The pack records usage from ordinary administration. The DBA rarely intends to invoke a paid option.
Opening the performance or tuning pages in Enterprise Manager can invoke pack features. The click becomes a usage record.
Running SQL Tuning Advisor is a direct Tuning Pack action. One run creates evidence Oracle can price.
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
The standard advice is that if the packs show usage, the obligation is settled and you simply pay. We disagree. In roughly half the audits Fredrik Filipsson defended, the Tuning Pack finding was incidental, short lived, and reversible, which made it negotiable rather than fixed. The buyer side move is to read the feature usage views yourself, document that usage was accidental and stopped, set CONTROL_MANAGEMENT_PACK_ACCESS to NONE going forward, and challenge both the scope and the timeline of the claim before accepting any number. An accidental click is an opening position for Oracle, not a verdict.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Tuning Pack is not bought by mistake. It is used by mistake. The defense starts with reading the same usage views the auditor will.
Four moves contain the risk before and during an audit.
Set CONTROL_MANAGEMENT_PACK_ACCESS to NONE on databases that are not licensed for the packs.
Review DBA_FEATURE_USAGE_STATISTICS regularly so you know what Oracle would find.
Make clear which Enterprise Manager screens and advisors invoke paid packs. Most accidental use is a training gap.
Where usage was accidental and stopped, contest the scope and timeline rather than accepting the full claim.
No. Tuning Pack is a separately licensed Oracle Database option, not a feature of Enterprise Edition. Using it without a license creates an obligation, even if the use was accidental through Enterprise Manager or an advisor.
Tuning Pack is licensed on the same metric as the underlying database, either per processor or per Named User Plus, as a percentage of the database license. It also carries annual support at the standard rate, which is the recurring cost.
Yes. Tuning Pack cannot be licensed alone. It requires the Diagnostics Pack, so the two are licensed and counted together. A Tuning Pack obligation always implies a Diagnostics Pack obligation as well.
Ordinary administration triggers it. Opening the performance or tuning pages in Enterprise Manager or running SQL Tuning Advisor invokes pack features and creates a usage record. The DBA rarely intends to use a paid option.
Set the database parameter CONTROL_MANAGEMENT_PACK_ACCESS to NONE on databases not licensed for the packs. This disables access to the Diagnostics and Tuning Pack features and is the strongest single safeguard against accidental usage.
Yes. Where usage was incidental, short lived, and stopped, the finding is negotiable rather than fixed. Document that the use was accidental, challenge the scope and timeline of the claim, and do not treat an accidental click as a settled bill.
Oracle reads the DBA_FEATURE_USAGE_STATISTICS view, which records management pack feature use whether intentional or accidental. Reviewing this view yourself before an audit tells you exactly what Oracle would find.
The Diagnostics Pack provides performance monitoring, AWR, and ADDM. The Tuning Pack adds SQL Tuning Advisor and SQL Access Advisor. Tuning requires Diagnostics, so the two are always licensed together as a pair.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Oracle Tuning Pack turns a database click into a license event. The buyer who sets the control parameter and reads the usage views controls the finding before the auditor writes it.
