Oracle options and management packs — price and trigger, line by line.

What is the difference between an option and a management pack?

An option extends what the database can do — Partitioning, RAC, encryption, in-memory processing. A management pack extends how you operate it — diagnostics, tuning, lifecycle automation, masking. Both are separately licensable add-ons to Enterprise Edition, both are licensed on the same per-processor metric as the database underneath them, and both record their use automatically in the data dictionary. The practical distinction for licensing is that management packs can be switched off at the database level via CONTROL_MANAGEMENT_PACK_ACCESS, while options must be designed out and remediated.

What does each Oracle Database option cost and what activates it?

List prices below are per processor on the Oracle Technology Global Price List, before discount and before the 22% annual support that recurs every year. Remember the processor count is cores × core factor — the same multiplier we unpack in Oracle processor licensing.

Two notes for 2026. Spatial is no longer separately licensed for most use — Oracle folded core Spatial functionality into Enterprise Edition from 19c, though Spatial features that depend on Partitioning still pull in the Partitioning licence. And Multitenant's free PDB allowance has shifted across releases; treat the high-water mark of pluggable databases as a metered count, not a fixed entitlement.

Which management packs activate silently?

All of them can, but Diagnostic and Tuning Pack are the two that activate through work a DBA does every week. Diagnostic Pack records use the moment an AWR report is generated, ADDM runs, or active session history is queried. Tuning Pack records use when SQL Tuning Advisor or SQL Access Advisor runs, or when the relevant Enterprise Manager screens are opened. Because these workflows are the default starting point for any performance investigation, they are the most common Oracle finding of all.

Tuning Pack carries a dependency worth knowing: it requires Diagnostic Pack. So a single SQL Tuning Advisor run can record use of two packs at once — $12,500 per processor combined at list, multiplied across every database the DBA touches. On a modest 20-processor estate that is a quarter of a million dollars from one click.

How do you stop unlicensed packs from activating?

Set CONTROL_MANAGEMENT_PACK_ACCESS to NONE to disable Diagnostic and Tuning Pack functionality entirely, or to DIAGNOSTIC if you licence Diagnostic but not Tuning. With the parameter set to NONE, the AWR and Advisor features are unavailable, so they cannot be triggered by accident. The cost is operational — you replace AWR/ADDM with Statspack and the Advisors with manual or third-party tuning. For most organisations the right answer is to decide deliberately: licence the packs you genuinely use, and hard-block the rest. Turning that licence-or-block decision into a permanent license cost reduction — rather than a one-off clean-up — is where an independent review pays for itself.

Options are different. There is no master switch; an option is "used" once its artefact exists. Remediation means removing the artefact — repartitioning to non-partitioned tables, decrypting columns, closing read-only standbys, dropping surplus PDBs — and then documenting non-use going forward. The historical row in DBA_FEATURE_USAGE_STATISTICS persists, so the value of remediation is to close the window of use, not to erase it. Running this yourself is the subject of our feature-usage audit guide, and engineered systems add their own wrinkle, covered in the Exadata guide.

Which findings should you chase first?

Sequence by expected exposure, not by alphabet. The cheap-per-processor packs that touch every database create the highest aggregate liability; the expensive options on big clusters create the highest single-instance liability. A pragmatic order:

Whatever the order, the discipline is the same one we apply in Oracle audit defence: find it yourself, decide licence-or-remove on each item, and re-check quarterly so nothing new accumulates between reviews.