Rows of database storage arrays in an enterprise data center
Oracle Advanced Compression

Oracle Advanced Compression. The option that switches itself on.

A buyer side guide to Oracle Advanced Compression licensing in 2026. How the option is metered, which features trigger it, and how a single COMPRESS clause becomes an audit finding.

Contact Us Oracle Practice
500+Enterprise clients
$2B+Under advisory
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Oracle Advanced Compression is a separately licensed option on top of Oracle Database Enterprise Edition. It is licensed per processor or per named user plus, on the same metric as the database it sits on, and it can be switched on by a single parameter or feature, which is exactly how it turns into an audit finding.

Key takeaways

  • Advanced Compression is a paid option on Enterprise Edition, not a base feature.
  • It is licensed on the same metric as the database, by processor or named user plus.
  • Several features quietly use it, including some forms of table and index compression.
  • Usage is recorded whether or not you bought it, which surfaces in an audit.
  • Basic table compression is free. Advanced row and other modes are not.
  • The control move is to confirm which compression you actually use before you renew.

This guide is for Oracle database and procurement teams sizing or defending Advanced Compression in 2026. Read it with the Oracle Database licensing guide and the Enterprise Edition options pricing and audit guide.

How is Oracle Advanced Compression licensed?

Advanced Compression follows the database it runs on. If the database is licensed by processor, the option is too. If it is named user plus, the option matches.

What metric does it use?

The option uses the same metric and the same minimums as Enterprise Edition. You cannot license the option on a smaller footprint than the database underneath it.

  • Processor: licensed on the same core factor as the database.
  • Named user plus: the same user count and per processor minimums apply.
  • Scope: every server where the feature is used must be covered.

What is free and what is paid?

Basic table compression for direct path loads is included with Enterprise Edition. The advanced modes are the paid part. Oracle sets the boundary in its licensing documentation.

  • Free: basic table compression on bulk load operations.
  • Paid: advanced row compression, advanced index compression, and more.
  • Check: the option also covers some backup and network compression.

How does it get switched on by accident?

Developers enable compression for performance, not licensing. A COMPRESS clause or an advanced mode can light up the option, and Oracle records the usage in feature tracking views regardless of entitlement.

What does Advanced Compression cost and where is the trap?

The list price sits in the mid range of Oracle options. The real exposure is not the sticker, it is paying for it across servers where it crept in unnoticed.

Oracle Advanced Compression, what triggers a license need

Feature Licensable Common trigger
Basic table compressionNo, included in EEDirect path bulk loads
Advanced row compressionYesCOMPRESS for OLTP clause
Advanced index compressionYesIndex rebuild with advanced mode
Backup compressionYes, some modesRMAN higher compression levels

How do you detect whether you use it?

Oracle tracks feature usage in DBA_FEATURE_USAGE_STATISTICS. Query it before any renewal or audit, because that view is the same evidence an Oracle auditor reads.

What do you do if it is on and unlicensed?

You either license the servers using it or you remove the usage and confirm the views are clean. Removing usage is only credible if you stop it and document the date.

Where is the negotiation leverage?

If the option crept in across a small number of servers, scope is your lever. Confine compression to licensed servers rather than buying the option estate wide to cover a few tables.

Nobody buys Advanced Compression on purpose at audit time. They buy it because a COMPRESS clause from three years ago is sitting in a feature usage view nobody checked.

What to do next

  1. Query DBA_FEATURE_USAGE_STATISTICS for compression features on every database.
  2. Separate free basic compression from the paid advanced modes.
  3. Map which servers genuinely need advanced compression for performance.
  4. Confirm your entitlements cover exactly those servers, no more.
  5. Where usage is accidental, remove it and document the change.
  6. Scope any purchase to the smallest licensed footprint that works.
  7. Re run the feature usage query before every renewal and audit.

Frequently asked questions

Is Oracle Advanced Compression included in Enterprise Edition?

No. Advanced Compression is a separately licensed option on top of Enterprise Edition. Only basic table compression for direct path loads is included. The advanced row, index, and backup modes require the paid option.

How is Advanced Compression licensed?

It is licensed on the same metric as the database it runs on, either per processor or per named user plus, with the same minimums. Every server where the advanced features are used must be covered.

How do I know if I am using Advanced Compression?

Query DBA_FEATURE_USAGE_STATISTICS, which records compression feature usage whether or not you own the option. That view is the same evidence an Oracle auditor reviews, so check it before any renewal.

Is basic table compression free?

Yes. Basic table compression for direct path bulk loads is included with Enterprise Edition. The paid option begins with advanced row compression, advanced index compression, and certain backup compression modes.

What triggers an Advanced Compression license need by accident?

A COMPRESS for OLTP clause, an index rebuild in an advanced mode, or higher RMAN compression levels can all light up the option. Developers enable these for performance without realizing they trigger a license requirement.

Can I remove usage instead of buying the option?

Yes, if you genuinely stop using the advanced modes and document the date. The feature usage views must show the usage has ended. Removing usage is only a credible defense when it is real and recorded.

Oracle ULA Decision Framework

The full oracle ula decision framework framework from the Oracle Practice.

Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, options, middleware, and applications estate.

Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.

No spam. We will only email you about this download. Privacy.
Run the software spend health check on your Oracle estate in under five minutes.
Open the Tool →
1
Parameter can trigger it
4
Common audit triggers
100%
Tracked in usage views
100%
Buyer Side

Nobody buys Advanced Compression on purpose at audit time. They buy it because a COMPRESS clause from three years ago is sitting in a feature usage view nobody checked.

Fredrik Filipsson
Co Founder and Group CEO. Ex Oracle, IBM, SAP.
Deep Library

More on this topic.

Oracle Practice →
Database servers in a data center
Oracle
Oracle Database Licensing Guide
How Oracle Database core, option, and metric licensing works for buyers.
14 min read
Finance team reviewing audit documents
Oracle
EE Options Pricing and Audit
Enterprise Edition option pricing and the audit traps to avoid.
15 min read
Data partition visualization on a screen
Oracle
Oracle Partitioning Policy
How the Partitioning option is licensed and where it gets triggered.
11 min read
Editorial boardroom interior

The advisor your vendors do not want.

500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.

Oracle brief. Once a week.

One short note on Oracle licensing moves, price list mechanics, audit posture, and the buyer side levers we run in client engagements. No noise.