Oracle Diagnostics and Tuning Pack Licensing: Key Facts and Compliance Actions

The Core Licensing Rule: Packs Are Not Included in Enterprise Edition

One of the most consistently misunderstood aspects of Oracle Database licensing is the relationship between Enterprise Edition and the management packs. Oracle Database Enterprise Edition provides core database functionality — storage management, SQL processing, high availability, security options — but it does not include the Diagnostic Pack or the Tuning Pack. These are separately priced, separately ordered products that extend EE with advanced monitoring and tuning capabilities.

The confusion arises because both packs are enabled by default in every EE installation. The CONTROL_MANAGEMENT_PACK_ACCESS initialisation parameter defaults to DIAGNOSTIC+TUNING, meaning both packs are active from the moment a new EE database is started. Oracle Enterprise Manager includes user interface features for both packs on every EE database home page. DBAs receive no warning that using the AWR report, checking Active Session History, or running SQL Tuning Advisor is a separately licensed activity — the tooling presents these features as integral to database management.

This design creates a systematic compliance problem across the Oracle enterprise customer base. Oracle's own LMS audit team reports that Diagnostic and Tuning Pack findings appear in 70 to 80 percent of all Oracle audits — making these packs by far the most common source of unplanned Oracle licensing costs in enterprise environments. The financial exposure is substantial: at list price, the Diagnostic Pack is $150,000 per processor perpetual ($7,500 per processor per year) and the Tuning Pack is $100,000 per processor perpetual ($5,000 per processor per year). Oracle support on both packs increases by 8% per year under Oracle's standard Software Update Licence and Support model.

What Specifically Requires a Pack Licence

Understanding precisely which actions trigger a pack licensing obligation is essential for managing compliance. Oracle defines the obligation based on feature usage recorded in DBA_FEATURE_USAGE_STATISTICS, not based on whether you knowingly or deliberately used a pack feature. If the feature usage view records activity, Oracle considers the feature to have been used, and the corresponding licence to be required.

Diagnostic Pack Triggers

The following actions require a Diagnostic Pack licence on any EE database instance where they occur. This list is not exhaustive but covers the most commonly encountered triggers:

• Running AWR reports using awrrpt.sql, awrrpti.sql, or any equivalent query against DBA_HIST_ views
• Viewing the AWR-based performance charts or baselines in Oracle Enterprise Manager
• Querying V$ACTIVE_SESSION_HISTORY or DBA_HIST_ACTIVE_SESS_HISTORY for ASH data
• Accessing the Automatic Database Diagnostic Monitor (ADDM) report in OEM or querying DBA_ADVISOR_TASKS/DBA_ADVISOR_FINDINGS where the advisor is ADDM
• Using the Performance Hub in Oracle Enterprise Manager (which aggregates AWR, ASH, and ADDM data)
• Any third-party monitoring tool that reads DBA_HIST_ views (V$SESSION queries are pack-free; DBA_HIST_ queries are not)

Tuning Pack Triggers

The Tuning Pack requires the Diagnostic Pack as a prerequisite — you cannot use Tuning Pack features without also licensing the Diagnostic Pack. Tuning Pack triggers include:

• Running SQL Tuning Advisor manually through OEM or DBMS_SQLTUNE
• The automated maintenance job SYS_AUTO_SQL_TUNING_TASK executing during the scheduled maintenance window (this runs by default on all EE databases)
• SQL profiles being implemented — whether manually accepted or automatically applied by SQL Tuning Advisor
• Running SQL Access Advisor through OEM or DBMS_ADVISOR with the SQL Access Advisor type
• Using the SQL Monitoring feature in OEM for completed statements (Real-Time SQL Monitoring also requires the Tuning Pack)

Immediate Compliance Actions: What to Do Right Now

If your organisation has not purchased the Diagnostic Pack and Tuning Pack, these are the immediate actions to take to stop ongoing accumulation of audit exposure.

Step 1: Disable Pack Access on All Unlicensed Databases

Connect to each Oracle Database Enterprise Edition instance that does not have a Diagnostic Pack and Tuning Pack licence and execute the following command as SYSDBA:

ALTER SYSTEM SET control_management_pack_access='NONE' SCOPE=BOTH;

This command takes effect immediately without requiring a database restart. SCOPE=BOTH ensures the change is applied to both the running instance (MEMORY) and the initialisation parameter file (SPFILE) so it persists across restarts. Document the date, time, and DBA who made this change for each database instance.

Step 2: Disable the Automated SQL Tuning Job

Even after setting CONTROL_MANAGEMENT_PACK_ACCESS = NONE, the automated SQL tuning maintenance job may continue to appear in scheduling tables. Disable it explicitly using the DBMS_AUTO_TASK_ADMIN package. Setting this parameter and disabling the maintenance job together provides the most complete stop to Tuning Pack usage accumulation.

Step 3: Review Third-Party Tooling

Audit every third-party database monitoring tool in your environment to determine whether it queries DBA_HIST_ views or uses DBMS_SQLTUNE or DBMS_ADVISOR. Tools that query only V$ views are pack-free; tools that access DBA_HIST_ views require the Diagnostic Pack. Contact the tool vendor or review the tool's documentation to understand its Oracle pack dependency. Where a tool does require pack access and you do not have a pack licence, either discontinue the tool or purchase the pack.

Step 4: Assess Historical Exposure

Run a query against DBA_FEATURE_USAGE_STATISTICS on each EE database to identify the FIRST_USAGE_DATE and LAST_USAGE_DATE for all pack-related features. This establishes your historical exposure profile — the time period for which Oracle could claim fees. This assessment should be treated as legally privileged if you are concerned about an imminent Oracle audit, and should be conducted with experienced Oracle licensing counsel.

Does SE2 Have Any Pack Obligation?

No. Oracle Diagnostic Pack and Tuning Pack are only available for Enterprise Edition. However, SE2 databases still contain the DBA_FEATURE_USAGE_STATISTICS view and still record feature usage data. If an SE2 database shows Diagnostic or Tuning Pack feature usage in this view, Oracle will typically argue that the database should have been licensed as EE from the point the EE-only features were first used — a much more expensive claim than simply adding pack licences to an SE2 system. This means that organisations running SE2 must be equally diligent about ensuring CONTROL_MANAGEMENT_PACK_ACCESS = NONE and that no EE-only features are used.

Negotiating Pack Licences: Timing and Tactics

If your assessment concludes that Diagnostic and Tuning Pack licences are required — either to retrospectively address historical exposure or to enable ongoing use — timing your purchase negotiation correctly is commercially critical. Oracle's fiscal year ends on 31 May, with Q4 running March to May. This is when Oracle's sales teams are under the most pressure to close deals and are authorised to offer the deepest discounts. Purchasing packs as a proactive licence true-up in Q4 — rather than under pressure during an audit — is consistently the most cost-effective approach.

The other critical commercial insight is that pack licences must be purchased at the same metric and quantity as the underlying Oracle Database EE licences. If you have 32 EE processor licences, you must purchase 32 Diagnostic Pack processor licences and 32 Tuning Pack processor licences. You cannot mix metrics (e.g., buying NUP packs for a processor-licensed EE database). The metric and quantity must match exactly.

If your organisation uses a ULA (Unlimited Licence Agreement) that covers Oracle Database EE, review whether the ULA also covers management packs. Some ULAs explicitly include Diagnostic and Tuning Packs within the unlimited scope; others explicitly exclude them. If your ULA is silent on this point, Oracle's position is typically that packs are excluded unless explicitly named — which is a negotiation point worth pursuing at next renewal or at ULA certification.

Cost Management Over the Licence Lifecycle

For organisations that do purchase Diagnostic and Tuning Pack licences, ongoing cost management requires the same discipline as managing any Oracle perpetual licence. Annual support fees at 22% of the perpetual licence cost increase at 8% per year — so a 32-processor pack suite that costs $320,000 in Year 1 support will cost approximately $435,000 in Year 5 and nearly $593,000 in Year 10. Over a 10-year lifecycle, cumulative support costs on the pack suite alone can exceed $4.7 million on a 32-processor environment.

Review your pack licence entitlement periodically to ensure it matches your actual processor licence count and deployment. If you have decommissioned servers or consolidated workloads, your processor count may have decreased — and pack licences above your current entitlement may be eligible for surrender or credit against other Oracle spend. Contact Redress Compliance or an independent Oracle licensing advisor to assess whether licence rightsizing is viable for your environment before approaching Oracle directly.

For a comprehensive technical deep-dive into every aspect of Diagnostic and Tuning Pack licensing — including AWR architecture, ASH sampling, ADDM analysis, and a detailed 5-step remediation plan — see our full expert guide to Oracle Diagnostic and Tuning Pack licensing.