Oracle Advanced Compression Licensing Explained

What does Oracle Advanced Compression license?

Oracle Advanced Compression licenses a bundle of compression and data movement features on top of Enterprise Edition, counted on the same processor base as the database beneath it. The headline features are OLTP table compression, which compresses data through normal inserts and updates rather than only bulk loads, advanced index compression, and a set of storage and data movement capabilities. Because the option attaches to the processor count, a database on 8 Processor licences needs 8 Advanced Compression licences to match, so the cost is never trivial. The point to hold onto is that this is one named option among many, each licensed separately, and each capable of being switched on without a purchase order ever being raised. The complete options picture is in the Oracle Database Licensing Guide.

Is any Oracle compression free?

Yes, basic table compression is free with Enterprise Edition, which is precisely what makes Advanced Compression dangerous, because the two live next to each other and the difference is a feature setting rather than a separate product. Basic compression applies to direct path bulk loads and needs no option. The moment a table is set to compress on ordinary inserts and updates, it has crossed into OLTP table compression, which is part of the paid Advanced Compression option. A DBA enabling compression to save storage, with the best intentions and no licensing context, can move a table from the free side to the paid side with one clause. The lesson is that compression is not a single free feature, it is a spectrum, and only part of it is included.

How does Advanced Compression become an audit finding?

Advanced Compression becomes an audit finding when Oracle feature usage data shows one of its features in use on a database that never licensed the option, which is most often the result of an accidental enablement rather than a deliberate choice. Many options install by default and a single setting can light one up, so the usage views can report Advanced Compression as used even where no one intended to deploy it. Oracle collection scripts read those views, and the preliminary finding follows. The buyer response is not to pay it but to investigate: confirm what is actually compressed, distinguish free basic compression from the licensable features, and establish whether the usage is real and ongoing or a historical flag from a one off action. See detecting accidentally enabled options for the detection method and disputing options enabled but never used for the response.

How do you manage Advanced Compression exposure?

You manage Advanced Compression exposure by keeping a clear inventory of which databases license the option and checking feature usage against that inventory on a regular cadence, so an accidental enablement is caught and reversed before an auditor finds it. Where the option is genuinely needed and used, license it cleanly to the processor count. Where a feature was switched on by mistake and is not required, disable it and record the date and reason, because the documentation is what turns a finding into a non event. The recurring theme across every Oracle option is the same: the cost of a quiet enablement is real, and the defence is knowing your own estate better than the auditor does.

What is the next step?

The next step is to run a feature usage check across every Enterprise Edition database, separate the free basic compression from the licensable Advanced Compression features, and resolve any accidental enablement before it reaches an audit. Download the options detection guide for the queries that distinguish free from paid compression and the template that records a clean disablement, and bring us your usage data when you want the check and the remediation done for you.