Advanced Compression is the Oracle option most likely to switch itself on without anyone deciding to use it. It prices per Processor, and a single compressed table is enough to make it an audit finding.
Oracle Advanced Compression prices per Processor and switches on through a single object attribute, often set by a migration tool. One compressed table can trigger the option across an entire licensed database.
Advanced Compression is the Oracle option most likely to switch itself on without anyone deciding to use it. It prices per Processor, and a single compressed table is enough to make it a finding.
This guide explains which features trigger the option, how the audit trap works, and how a buyer closes it.
Advanced Compression is a per Processor option on Enterprise Edition. It covers a family of compression and storage features beyond basic table compression.
The option includes OLTP table compression, Advanced LOB compression and deduplication, Advanced Index compression, and several backup and network compression features. Using any one of them consumes the option, as the Oracle database technologies documentation confirms.
Basic table compression for direct path loads is free with Enterprise Edition. The moment you use OLTP compression for ongoing writes, you are in licensed territory. The line is easy to cross by accident.
White Paper · Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
The trap is that compression is a property of an object, not a separately installed feature. A developer or a migration tool sets a compression attribute, and the option is in use.
Where Advanced Compression switches on silently
| Action | Feature consumed | How it happens | Defense |
|---|---|---|---|
| Create table with OLTP compression | OLTP compression | Developer attribute | Review DDL standards |
| Migration tool default | OLTP compression | Tool sets attribute | Audit import scripts |
| Compress LOB columns | Advanced LOB | Schema design | Check LOB storage |
| SecureFiles deduplication | Advanced LOB | Storage option | Audit SecureFiles |
Data pump and third party migration tools sometimes apply compression attributes by default. A migration that looked clean can leave OLTP compression set across the target schema, a use the Oracle price list prices per Processor.
Query the feature usage views and the data dictionary for compressed objects. The DBA_TABLES and DBA_LOBS views show compression settings directly.
Like other options, it scales per Processor. One compressed table on a large cluster implies the option across every licensed core on that database.
Build a complete inventory of compressed objects and the compression type. Separate free basic compression from licensed OLTP compression. The inventory is both your defense and your remediation plan.
The standard advice is to license Advanced Compression across the estate because compression is everywhere and an audit will find it. We disagree. In roughly three out of four estates we have swept, the licensed compression in use was set by accident, usually by a migration tool default, on objects where compression delivered little benefit. The buyer side move is to inventory every compressed object, revert accidental OLTP compression to basic or none where it adds no value, and license the option only on the databases where compression is genuinely required. Paying estate wide for a setting a tool flipped is the most avoidable Oracle cost there is.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Nobody buys Advanced Compression. A migration tool buys it for them, one default attribute at a time, and the audit collects.
Defense is inventory, remediation, and DDL discipline so it does not recur.
List every table, index, and LOB with a compression attribute, and the compression type. This separates free from licensed use.
Where licensed compression adds no value, revert it to basic or none. This removes the usage and the exposure together.
Advanced Compression is a per Processor option on Enterprise Edition. It covers OLTP table compression, advanced LOB compression and deduplication, advanced index compression, and several backup and network compression features.
Yes. Basic table compression for direct path bulk loads is free with Enterprise Edition. OLTP compression for ongoing writes, advanced LOB compression, and advanced index compression all require the Advanced Compression option.
Compression is a property of a database object, not a separately installed feature. A developer or a migration tool sets a compression attribute, and the licensed option is immediately in use without any deliberate decision.
Data pump and some third party migration tools apply compression attributes by default. A migration that looked clean can leave OLTP compression set across the target schema, consuming the licensed option.
Query the database feature usage views and the data dictionary. The DBA_TABLES and DBA_LOBS views show compression settings directly, letting you separate free basic compression from licensed OLTP and advanced compression.
The option prices per Processor at the same scale as the database. A single compressed object can imply the option across every licensed core on that database, with back support compounding the exposure.
Yes. Inventory every compressed object, then revert accidental OLTP or advanced compression to basic or none where it adds no value. This removes both the usage and the audit exposure together.
Not by default. Inventory usage first, revert accidental compression, and license the option only on databases where compression genuinely delivers value. Paying estate wide for a tool set default is avoidable.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
