Oracle Database Management Packs: Which Are Licensable

What Are Oracle Database Management Packs?

Oracle management packs sit in a deliberately confusing place. They are not part of the base Enterprise Edition license, yet many of them are installed and active the moment you install Enterprise Edition. There is no separate download, no installer checkbox, and frequently no warning. The features simply work — and that is the trap. Oracle's commercial model relies on customers using paid functionality without realising it carries a price tag, then converting that usage into a back-license claim during an audit.

The packs divide into two families. The database-resident packs — Diagnostics and Tuning — live inside the database kernel itself and are reached through AWR, ADDM, SQL Tuning Advisor, and the performance views. The Enterprise Manager packs — Database Lifecycle Management, Cloud Management, and Data Masking & Subsetting — are layered on top of Oracle Enterprise Manager (Cloud Control) and are consumed through its console. Both families are licensed on the database they manage, not on the management server, which is a point Oracle's LMS team enforces aggressively.

Which Oracle Management Packs Are Licensable?

Five database management packs require a separate license. The table below lists each pack, what it does, and its approximate 2026 list price per processor. These figures come from the Oracle Technology Global Price List (2026); real-world purchase prices land well below list after negotiation, but back-license settlements are calculated at or near list.

One important clarification: the Tuning Pack has a dependency on the Diagnostics Pack. You cannot license the Tuning Pack without also holding the Diagnostics Pack, because the Tuning Pack's advisors consume AWR data that only the Diagnostics Pack exposes. In practice this means a Tuning Pack exposure almost always carries a Diagnostics Pack exposure with it — a detail Oracle uses to inflate claims.

Note what is not on this list. The free Enterprise Manager base functionality — basic monitoring, target discovery, the database home page — does not require a pack. The confusion arises because the paid features are interleaved with the free ones in the same console, with no visual indicator separating them. For a fuller view of the surrounding option landscape, see our Oracle Database licensing guide.

What Triggers the Oracle Diagnostics Pack?

The Diagnostics Pack is the most commonly triggered paid option in the entire Oracle estate. Across our engagements, accidental Diagnostics Pack usage appears in more than 40% of Enterprise Edition environments we review (Oracle Licensing Experts, 2026). The reason is that the features it gates are the exact tools every DBA reaches for first when investigating a performance problem.

Specific triggers include: running an AWR report (awrrpt.sql), generating an ASH report, querying any DBA_HIST_* view, viewing the "Performance Hub" or "Top Activity" pages in Enterprise Manager, and enabling automatic ADDM analysis. Even the default automatic AWR snapshot collection — which Oracle enables by default at hourly intervals — has been argued by LMS auditors to constitute usage, although that position is contestable and worth challenging.

-- Feature usage Oracle records and LMS reads
SELECT name, detected_usages, currently_used,
       first_usage_date, last_usage_date
FROM   dba_feature_usage_statistics
WHERE  name LIKE '%Diagnostic Pack%'
   OR  name LIKE '%AWR%'
   OR  name LIKE '%Automatic Workload Repository%';

If you have not licensed the Diagnostics Pack, the safe configuration is to set CONTROL_MANAGEMENT_PACK_ACCESS=NONE, which blocks AWR, ADDM, and ASH entirely. Be aware this also disables some functionality DBAs rely on, so the decision is a genuine trade-off rather than a free fix.

What Triggers the Oracle Tuning Pack?

The Tuning Pack automates SQL optimization. Its headline feature, the SQL Tuning Advisor, analyses a problem statement and recommends indexes, SQL profiles, or restructured statements. It is invoked through Enterprise Manager's "Tuning" workflows and through the DBMS_SQLTUNE package. The Automatic SQL Tuning task, which Oracle schedules in the default maintenance window, runs the advisor automatically every night — meaning the Tuning Pack can be consumed without any human action at all.

This automatic-maintenance trigger is one of the most defensible points in a Tuning Pack dispute. If the only recorded usage is the default Automatic SQL Tuning task that Oracle itself scheduled, an experienced advisor can argue the customer never deliberately exercised the feature. Our Oracle audit defense team regularly narrows Tuning Pack claims on exactly this basis.

Are the Database Lifecycle and Cloud Management Packs Licensable?

Yes. Both the Database Lifecycle Management Pack (DBLM) and the Cloud Management Pack for Oracle Database are separately licensed, and both are consumed through Oracle Enterprise Manager rather than the database kernel.

The Database Lifecycle Management Pack covers automated provisioning, patch automation, configuration management, the compliance framework, and database cloning. At roughly $12,000 per processor per year it is the most expensive database management pack on the list. Crucially, it is licensed on every database target it manages — so an estate of 50 databases automated through DBLM requires the pack on all 50, not on the management server. Many enterprises discover DBLM exposure only when they adopt Enterprise Manager's patch automation to save DBA effort, unaware that the labour saving carries a per-processor licence cost.

The Cloud Management Pack enables database-as-a-service, self-service provisioning, metering, and chargeback inside Enterprise Manager. It is the pack organisations trip over when they build an internal "private cloud" portal for database provisioning. Setting up a self-service catalogue and chargeback dashboards is precisely the activity it gates.

What About the Data Masking & Subsetting Pack?

The Data Masking and Subsetting Pack is a separately licensed Enterprise Manager pack that masks sensitive production data and creates smaller, representative subsets for development and test environments. At roughly $11,500 per processor per year, it is frequently adopted for GDPR, HIPAA, or PCI-DSS data-protection programmes — and that is the irony: an organisation enables it to improve compliance and inadvertently creates an Oracle licensing compliance gap.

The pack is licensed on both the source database (where masking definitions are applied) and any target databases where masking or subsetting operations execute. Because masking is usually run against multiple non-production environments, the processor count adds up quickly. Organisations that adopt the pack through Enterprise Manager's "Application Data Modeling" and "Data Masking" workflows should assume every database touched by those workflows is in scope.

If data masking is a genuine requirement, it is often cheaper to license the pack legitimately within a negotiated Oracle contract negotiation than to settle a back-license claim later. Where masking can be achieved by third-party tooling that does not depend on the Oracle pack, that route avoids the option cost entirely.

How Does Oracle Detect Management Pack Usage?

Oracle LMS detects management pack usage through the database's own feature-tracking machinery, which records usage automatically and retains it for roughly a year. The primary evidence source is the DBA_FEATURE_USAGE_STATISTICS view, populated weekly by an internal job. It records each tracked feature, whether it is currently used, how many times it has been detected, and the first and last usage dates.

SELECT name, version, detected_usages,
       currently_used, first_usage_date, last_usage_date
FROM   dba_feature_usage_statistics
WHERE  name IN ('Diagnostic Pack','Tuning Pack',
                'Data Masking Pack','Real Application Testing',
                'Automatic Workload Repository')
ORDER  BY name;

For Enterprise Manager packs, LMS additionally queries the OEM repository and the management pack access tables to establish which packs were configured against which targets. The combination of database-side feature usage and OEM-side configuration is difficult to rebut once recorded — which is why prevention matters far more than after-the-fact argument. That said, the dates and counts these views return are routinely misread by LMS auditors, and the DBMS_FEATURE_USAGE_INTERNAL tracking can over-report. A forensic review of the actual usage records frequently shows the real exposure is narrower than the headline claim. For the broader audit mechanics, see our guide to Oracle LMS audit scripts.

How Do You Right-Size Management Pack Exposure?

Right-sizing management pack exposure is a four-step discipline: measure, block, document, and decide. The earlier you act — ideally before any audit letter arrives — the more options you keep.

1. Measure first. Run the feature-usage queries across every Enterprise Edition database, production and non-production alike. You need to know your true position before Oracle establishes theirs. A forensic compliance review produces the same evidence base LMS would, but on your side of the table.
2. Block accidental access. For databases where you do not intend to license the Diagnostics or Tuning packs, set CONTROL_MANAGEMENT_PACK_ACCESS=NONE and unconfigure the relevant OEM packs. This stops new usage from accruing.
3. Document the remediation date. Capture the configuration change and the post-change feature-usage output as evidence. If Oracle later claims usage, you can show the window in which the feature was disabled.
4. Decide on legitimate licensing. Where a pack delivers real value — DBLM for patch automation, Data Masking for a privacy programme — license it deliberately and negotiate it into a wider agreement, where the incremental cost is far lower than a standalone settlement.

The strategic point is that management pack exposure is almost always cheaper to fix proactively than reactively. In our engagement data, customers who right-size before an audit pay a small fraction of what they would surrender in a back-license settlement, where Oracle applies list pricing plus a 22% support uplift across the full detected period (Oracle Licensing Experts, 2026). Our case studies document several seven-figure claims reduced through exactly this approach.

Frequently Asked Questions