Oracle Database EE Options: Complete List, Pricing & Audit Risk

The Hidden Cost of Enterprise Edition Options

Oracle Enterprise Edition (EE) starts at $47,500 per processor. It is a substantial licensing foundation. But the real cost burden emerges when you enable optional features. Oracle publishes 17 or more add-ons for EE, each priced between $11,500 and $15,000 per processor annually. Many of these options can be enabled with a single command, are turned on by default during certain installations, or are activated silently during upgrades. Oracle does not prevent unlicensed option usage. Instead, the company detects usage retroactively through audit scripts and bills organizations for years of noncompliant usage, sometimes totaling hundreds of thousands of dollars in retroactive true-ups.

Over 500-plus engagements, I have seen this pattern consistently: organizations deploy EE believing they have licensed only the base product, only to discover during an Oracle LMS audit that performance monitoring or data compression features have been active for three years without license coverage. This article walks through the complete list of EE options, their processor and Named User Plus pricing models, how Oracle detects usage through the DBA_FEATURE_USAGE_STATISTICS view, real-world audit exposure, and tactical remediation strategies to reduce compliance risk.

The 17-Plus Oracle EE Options and Their Pricing Structure

Oracle offers a sprawling portfolio of optional products and packs for Enterprise Edition. The core options available include Partitioning, Advanced Compression, Advanced Security, Database Vault, Real Application Clusters One Node (RAC One Node), and In-Memory Column Store (IMDB). Beyond these, Oracle provides Data Masking and Subsetting Pack, Diagnostics & Tuning Pack, Multitenant, and others. Each option carries its own licensing tier and is billed independently.

Partitioning allows horizontal data distribution across table segments. It costs $11,500 per processor or $230 per Named User Plus license. Advanced Compression reduces storage by compressing tables, indexes, and archive logs at the cost of increased CPU overhead. It is also priced at $11,500 per processor or $230 per NUP. Advanced Security, which includes encryption features like Transparent Data Encryption (TDE), runs $15,000 per processor or $300 per NUP. Database Vault, which restricts even privileged user access within the database, is $11,500 per processor or $230 per NUP. Each option attracts the same 22 percent annual support and maintenance fee applied to your base EE license.

A fully loaded EE deployment with several options enabled can cost 2 to 3 times the base database license. An organization running EE on 4 processors with Partitioning, Advanced Compression, and Advanced Security would incur base EE costs of $190,000 annually, plus $46,000 for Partitioning, $46,000 for Compression, and $60,000 for Advanced Security. That is $342,000 per year, or nearly seven times the cost of Standard Edition 2. This pricing structure frequently creates hidden cost liability that emerges during audit cycles.

How Oracle Detects Option Usage During Audits

Oracle LMS (License Management Services) uses a sophisticated detection mechanism centered on the DBA_FEATURE_USAGE_STATISTICS view. This view has existed since Oracle 10g and records every feature used across a database system since the view was first sampled. When you enable Partitioning, Advanced Compression, or Advanced Security features on a table, that usage is recorded with a timestamp. When Oracle runs its audit scripts, it queries this view to identify option usage without license coverage.

The mechanism is fundamentally unfair to customers: Oracle does not warn you that a feature is unlicensed. It does not prevent the feature from being used. Instead, it silently records usage and bills retroactively. The LMS audit script analysis document details exactly how these queries work. Many DBAs do not understand which features require options. A performance consultant might recommend enabling Partitioning to improve query speed. A security team might implement Transparent Data Encryption across all production databases. Neither action will trigger a license error. Both will show up on an audit bill months or years later.

Consider a real case: A global logistics firm needed performance improvements on a large inventory table. The DBA enabled Partitioning to distribute the table across 16 segments for faster queries. This improved performance dramatically. Three years later, Oracle audited the infrastructure and found Partitioning was active but unlicensed. The audit bill totaled $400,000: three years of retroactive Partitioning option fees plus interest. The company had not knowingly violated licensing. It simply did not understand that Partitioning was a paid option. This scenario repeats constantly in enterprise audits.

Our audit risk assessment tool scans your DBA_FEATURE_USAGE_STATISTICS view and identifies option usage without licensing. This scan often reveals unlicensed features long before Oracle's audit team discovers them, giving you time to remediate or negotiate licensing adjustments.

Real-World Audit Risk: The $400K Invoice and Multitenant Trap

The Partitioning case illustrates the financial exposure that emerges from option misuse. But the risk intensifies when you combine multiple options or when Oracle changes definitions of what requires licensing. As of Oracle 19c, Multitenant is a required paid option for any database running more than one pluggable database (PDB). Many organizations have been consolidating workloads into multitenant architectures without realizing that each additional PDB requires a separate Multitenant license purchase. If you are running three PDBs on a single server, Oracle now claims you owe fees for two additional Multitenant licenses on top of your base EE fee.

This creates a compounding effect: Multitenant can cost $15,000 or more per processor, and enabling it retroactively can incur years of back-fees. An organization with four processors running two additional PDBs would face approximately $120,000 in annual Multitenant costs plus retroactive billing for prior years.

To stay ahead of these risks, subscribe to Vendor Shield, our monitoring service that alerts you to Oracle policy changes and their retroactive implications before audit exposure emerges. Vendor Shield has flagged similar retroactive traps with other vendors and helped clients avoid audit surprises.

Remediation: Feature Removal and Access Control

If you discover unlicensed option usage before an audit, several remediation paths are available. The most straightforward is feature removal. Oracle provides the chopt utility, which physically removes option binaries from your installation, preventing accidental use. You can also set the CONTROL_MANAGEMENT_PACK_ACCESS parameter to "NONE" to block usage of Diagnostics & Tuning Pack features, even if the binaries remain installed.

For Partitioning, you can move partitioned tables to unpartitioned equivalents, though this is labor-intensive and may impact performance. For Advanced Compression, you can disable compression on specific tables or tablespaces. For Advanced Security and TDE, you can disable column encryption on non-critical tables while maintaining coverage on sensitive data.

These remediation steps require careful planning and testing to avoid downtime or application failures. Our advisory team helps organizations map remediation steps specific to your infrastructure and option deployment. We coordinate with your DBA team to validate that feature removal does not impact production systems.

If you are facing an Oracle audit with option exposure, negotiation is often your strongest tool. Organizations can leverage our consulting services to engage Oracle's sales team directly and negotiate reduced true-up fees in exchange for licensing compliance going forward. Many organizations reduce their audit exposure by 40 to 60 percent through skilled negotiation.

Strategic Licensing: Processor vs. Named User Plus Pricing

Oracle offers two pricing models for options: processor-based and Named User Plus (NUP) based. If your user base is small (fewer than 25 users per processor), NUP pricing is often more economical. If your user base is large or includes casual users, processor licensing becomes unavoidable. Use our licensing calculator to model both scenarios and identify the cost-optimal path for your infrastructure. Some organizations benefit from licensing only critical options (Advanced Security on sensitive schemas) while avoiding others (Partitioning on non-critical tables), reducing their total EE option costs by 30 to 40 percent.

Minimum Named User Plus requirements also apply to options. You must purchase at least 25 NUP licenses per processor regardless of your actual user count. If you exceed the per-processor break-even point, processor licensing becomes mandatory. This rule creates hidden complexity in option pricing and is often a source of negotiation leverage during renewal cycles.

For cross-cluster guidance on related EE features, review our articles on Diagnostics and Tuning Pack licensing, Partitioning feature rules, and Advanced Security and TDE licensing.