Every Exadata sale includes storage server software, but the licensing rules are buried in the Database Licensing Information User Manual rather than the headline price list. Smart Scan, Storage Indexes and Hybrid Columnar Compression are free with Exadata; Database In-Memory, Advanced Security and Advanced Compression are not - and the procurement gap between the two costs Fortune 500 customers seven figures at audit. This article decodes the 2026 picture: what is free on the cells, what triggers a Database EE option, how Oracle LMS pulls the evidence, and the five contract levers that survive renegotiation.
Every Exadata sale - on-prem rack, ExaCC, ExaCS, Database@Azure, Database@AWS - includes storage server software whose licensing rules are buried in the Oracle Database Licensing Information User Manual rather than in the headline price list. The result is predictable: customers buy Oracle Database Enterprise Edition (EE) on the database servers, assume the storage cell software is part of the machine cost, and discover at the next LMS audit that several storage-cell features needed separate Processor entitlements - or that the bundled features they thought were free become chargeable the moment they enable a single advanced data-warehouse pattern.
This article decodes Exadata storage cell licensing in 2026: which storage server features are free under the EE licence, which are included with the Exadata stack itself, which require a separate Database EE option, and which only ship on specific Exadata deployments. The wider Exadata framework lives in the Oracle Database Licensing Guide; the wider compliance framework in the Oracle Compliance Master Guide; the LMS audit framework in the Oracle Audit Guide. Read those alongside.
The three numbers that matter: roughly 30% of mid-size Exadata audits we run surface unallocated Hybrid Columnar Compression (HCC) usage; another 20% surface Smart Scan dependency on options the customer never bought; and almost every multi-tenant Exadata cluster carries some Storage Indexes / Storage Server software exposure the customer cannot explain without the source LMS evidence map. None of these are obvious from the storage-cell SKU sheet alone.
An Exadata storage cell is a 1U or 2U server (depending on generation) that combines Intel CPUs, NVMe flash, and 25/100 Gbit RoCEv2 networking, running Oracle's purpose-built storage server software stack. The components that matter for Exadata storage cell licensing are:
That last point is the trap. The storage cell offload features are free, but several of them only become useful when paired with a Database EE Option licensed on the database servers. The procurement team buys the rack, sees 'HCC included', and misses that the In-Memory advantage requires a $23,000-per-Processor option licence on every activated database core.
The clean separation for an Exadata buyer to internalise is: what's free on the cells, what's chargeable on the database servers, and what's chargeable everywhere. Here is the 2026 picture.
| Feature | Free on Exadata | Requires Option |
|---|---|---|
| Smart Scan, Smart Flash Cache, Storage Indexes, IORM | Yes | No |
| Hybrid Columnar Compression (Exadata, ExaCC, ExaCS, ZS3) | Yes on Exadata family | Advanced Compression on non-Exadata |
| Database In-Memory columnar acceleration on flash | Free cell behaviour | Database In-Memory option ($23K/Proc list) |
| Advanced Index Compression in storage | No | Advanced Compression option |
| Encryption of data at rest in cells (Transparent Data Encryption) | No | Advanced Security option |
| Partition-based offload + Partition-wise smart scan | Free cell behaviour | Partitioning option on database |
| Snapshot-based test/dev clones on cells (Exadata Database Service Sparse Clones) | Free on ExaCC, ExaCS, Exadata X11M | No |
| Exadata Auto Indexing | No | Database In-Memory + ADW Auto-Index path |
| Multitenant offload across PDBs | Storage cell sees PDBs as databases | Multitenant option above 3 PDBs |
The pattern: the cell does the offload work for free, but the feature you want is only useful when the database server is licensed for the relevant Database EE Option. Partitioning is the classic example - on a non-Partitioned table the storage cell still smart-scans, but it cannot prune partitions because the partition metadata does not exist on the database server. The cell side is free; the database side is $11,500 per Processor at list.
We map your cell-side feature usage to your contracted entitlements, identify the audit gap, and propose the minimum-cost remediation path - typically before any LMS letter arrives. Fixed-fee, 2-3 weeks.
HCC was the standout Exadata storage-cell capability for a decade and remains the most audited. It is free on the Exadata family - that's the part the Oracle sales rep says correctly. The part that gets lost: HCC has four compression levels (QUERY LOW, QUERY HIGH, ARCHIVE LOW, ARCHIVE HIGH) and each carries a different operational profile. Customers routinely enable QUERY HIGH or ARCHIVE HIGH on Production tables, get the compression benefit, and then forget that when they replicate the database to a non-Exadata test environment - or to a third-party platform during a database migration - the HCC compression is unsupported and the operation fails. That triggers a remediation conversation that often surfaces other licensing exposure.
The HCC compatibility rules are strict. HCC is supported on:
HCC is not supported on Oracle Database Appliance (ODA), generic SAN, third-party storage, or VMware-backed Oracle databases. A common migration pattern - lift an Exadata-resident database into a non-Exadata Azure or AWS VM with attached block storage - silently breaks HCC. The decompression cost on the destination platform is high. Plan the compression conversion as part of the migration scope, not as a discovery item.
The audit signal Oracle LMS pulls: a query against DBA_FEATURE_USAGE_STATISTICS filtered on HCC_* features. If the customer has run HCC on a non-Exadata target, the entry appears - and the customer needs Advanced Compression at $11,500 per Processor across the full activated core count of the non-Exadata platform.
Smart Scan is the marquee Exadata cell feature. It moves SQL predicate filtering from the database server down to the cell, meaning the cell returns only the rows that matched the WHERE clause. The CPU work on the database server drops by 60-95% on data-warehouse workloads. Smart Scan is free with Exadata - no separate licence required.
But the workload patterns that maximise Smart Scan benefit overlap with chargeable options:
Storage Indexes are an in-memory min/max metadata structure maintained by the cell itself, kept entirely outside the database server. They are not the same as database B-tree indexes. Storage Indexes accelerate range filters and equality filters on numeric and date columns, and they are free with Exadata. They are also the explanation behind a common audit finding pattern - the customer sees inexplicably fast scan performance on a workload that should have been I/O-bound and concludes the cell is 'doing something special'. It is - but it is free.
The Oracle Database Licensing Information User Manual is explicit that Smart Scan and Storage Indexes do not require additional licensing on top of EE. Save that reference for audit defence.
The single highest-impact paid combination on the Exadata storage cell is Database In-Memory + Exadata Smart Scan. The cell materialises the In-Memory column store into flash, the database server runs vectorised SIMD operations on the columnar format, and the result is single-digit-millisecond response on analytics queries against multi-terabyte fact tables.
The economics: Database In-Memory is $23,000 per Processor at list, applied to the activated core count of the database servers (not the cells). On a 32-core ExaCC Quarter Rack at 0.5 Core Factor that is 16 Processors at $23K each = $368,000 list, before discount. Discounts on In-Memory at Exadata renewal typically reach 65-80% in our negotiations, so the effective price is usually $75,000-$130,000 plus 22% annual support.
Cell-side: free. The Exadata cell does not require a separate In-Memory cell licence; the cell behaviour is bundled.
The pattern we see at audit: customer evaluates In-Memory on a single test database, leaves the option enabled on a Production database for an experiment, forgets, and three years later DBA_FEATURE_USAGE_STATISTICS shows 'In-Memory Column Store' as ever-used. The LMS interpretation is that In-Memory is in-scope across the full activated core count. The remediation cost on a 96-core ExaCC half-rack is typically $1.1M-$1.6M.
Pre-emptive: disable In-Memory entirely on every database that does not need it. Set INMEMORY_SIZE = 0 and document it. This is the single most cost-effective Exadata audit-defence move we recommend.
Two more paid options frequently turn up in Exadata storage-cell audit findings.
Transparent Data Encryption (TDE) - part of the Advanced Security option. TDE encrypts data at rest in the storage cells. It is widely deployed because most enterprise security frameworks require encryption at rest as a baseline control. TDE list price is $15,000 per Processor; on a 32-Processor activated core count that is $480,000 list. Discounts at Exadata renewal commonly reach 60-75%.
The audit risk: a customer enables TDE on one tablespace on one database to satisfy a security audit, and ends with the entire database licensed for Advanced Security under LMS interpretation. The remediation discussion is harder because the security audit and the licence audit pull in opposite directions - the customer cannot turn TDE off without breaking the security baseline.
The defence: license Advanced Security across the full activated core count of any Exadata cluster running TDE. This is one of the few options we recommend full-pool licensing for - the partial licensing path is operationally fragile.
Advanced Compression - separate from HCC (which is free on Exadata). Advanced Compression covers OLTP table compression, index compression, RMAN backup compression and Data Pump compression. Many Exadata customers turn on at least one of these features for operational reasons (smaller backups, smaller indexes). The audit signal is DBA_FEATURE_USAGE_STATISTICS entries for 'Heat Map', 'Advanced Index Compression' or 'Data Pump Compression'. Advanced Compression is $11,500 per Processor at list.
The pattern that survives audit: either license Advanced Compression across the cluster or disable the features explicitly. Document the disable. Do not rely on 'we never turned it on' - DBAs frequently enable these features tactically and forget.
The standard Oracle LMS Exadata audit script pulls DBA_FEATURE_USAGE_STATISTICS, V$OPTION, the cell software version (cellcli list cell output), the cell-side compression usage statistics, and the database-side option usage. Cross-referencing these against contracted entitlements is the first 70% of the audit response.
The customer-side preparation we recommend before any Exadata audit notification arrives:
The pre-emptive review is what the Audit Defence service delivers. The wider audit timeline and tactic playbook is in the Oracle Audit Guide; the negotiation overlay during contract refresh is in the Oracle Negotiation Guide; the broader Exadata cost framework is in the ExaCC pricing anatomy article.
Exadata storage cell licensing is contractually negotiable - more so than most customers realise. Five levers that work in 2026:
The negotiation tactic library for Exadata renewals is in the Oracle Negotiation Guide; the support-cost reduction framework is in the Support Cost Reduction Guide; cluster-level cost trade-offs are unpacked in the Exadata on-prem vs ExaCC vs ExaCS decision matrix and the Exadata X11M vs X10M vs X9M generations analysis.
Exadata storage cell licensing rewards customers who internalise three rules: free cell-side features only realise their value when paired with paid database-server options; the audit signal lives in DBA_FEATURE_USAGE_STATISTICS on the database, not on the cell; and the renewal is the right moment to lock the option pricing for the lifecycle of the platform.
The default action for any Exadata customer who has not run the diagnostic in the last 12 months is to run it now. The findings are reversible while still pre-audit; they are not reversible once Oracle LMS has the scripts.
For deal-specific support - storage-cell audit defence, ExaCC contract negotiation, In-Memory pricing benchmarking, or migration-driven HCC strategy - the independent Cloud & OCI Advisory and Compliance Review services are designed for this exact pattern. The wider Exadata reading list: ECPU vs OCPU on Exadata, ExaCC minimum activation, BYOL vs LI on ExaCC, and Exadata Cloud Service (ExaCS) on OCI.
Yes, on the Exadata family - X-series on-premise, ExaCC, ExaCS, Database@Azure/AWS/Google Cloud, and Oracle ZFS Storage. HCC is included with the platform licence. It becomes chargeable (under Advanced Compression at $11,500 per Processor) when used on non-Exadata storage or when HCC-compressed data is decompressed on a non-Exadata destination as part of a migration.
No. Smart Scan, Smart Flash Cache, Smart Flash Log and Storage Indexes are all free with Exadata under the standard Database EE licence on the database servers. The cell-side software is bundled with the platform. The Oracle Database Licensing Information User Manual is explicit on this.
No. Database In-Memory requires the Database In-Memory option at $23,000 per Processor list across the activated core count of the database servers. The cell-side flash columnar materialisation is free, but the database-side option is a paid Oracle Database EE option. A single instance of usage triggers full-cluster scope under standard LMS interpretation.
High. The Advanced Compression option covers OLTP table compression, advanced index compression, RMAN backup compression and Data Pump compression. A single usage event in DBA_FEATURE_USAGE_STATISTICS triggers full-cluster option scope at $11,500 per Processor on the activated core count. The defence is either full-pool licensing or explicit disable with documentation.
Not without Advanced Compression on the destination. HCC is platform-specific to the Exadata family and Oracle ZFS. If you replicate HCC-compressed data to a non-Exadata target (a generic Azure VM, an AWS EC2 instance, an on-premise SAN), the decompression on the target requires Advanced Compression to be licensed at the target's full Processor count. Plan compression conversion as part of any cross-platform replication.
Twice a month. Oracle cloud, DRCC, ExaCC contract patterns, audit-defence tactics and BYOL maths. Written by former Oracle insiders.
No spam. Unsubscribe any time. Independent - not affiliated with Oracle Corporation.