During an internal license audit, using Advanced Compression Option (ACO) in the context of Oracle Analytics Server (OAS) came up as a topic. Data from the database on which the OAS application schemas were installed showed that some objects – particularly LOB type columns – had been created using SecureFile compression mechanisms, which in some cases could indicate the use of the option requiring a separate license.

The concern was whether such use of ACOs was due to the operation of the OAS itself, or whether it was an operation, requiring additional licensing. Sources of concern included an entry in DBA_FEATURE_USAGE_STATISTICS that suggested the use of a compression option.For verification purposes, the following query was performed:

The following graphic illustrates the results obtained:

Technical analysis showed that the source of the compression was not manual user intervention, but the default operation of the Repository Creation Utility (RCU), which creates the schemas necessary to run OAS. When the db_securefile parameter in the database has a value of PREFERRED (which is the default setting), Oracle automatically creates SecureFile columns with compression if the feature is available.

„The repository creation utility by default will make use of advanced compression feature when the feature is supported at the Database level. To be clear, if RCU is configured to use an Oracle database, the RCU table may be created with ADVANCED compression”*

According to Oracle’s official documentation, described in the note “Impact And Licensing Considerations Of SecureFile Compression In OAS RCU Database (Doc ID 3079811.1)”, this situation does not require an additional license, as long as the compression applies only to automatically created OAS schemas:

„ OAS is utilizing Advanced Compression ONLY for RCU-created metadata schemas and as caused by the default RCU application, Customers should document this creation and usage accordingly to avoid adverse licensing implications. Any other use of Advanced Compression MUST be licensed accordingly”*

In practice, this means that if ACO is used exclusively by automatically created OAS metadata schemas and compression has been enabled by the default RCU behavior, there is no need for an additional Advanced Compression license. It is crucial not to go beyond this scope and not to use this option in other contexts, as licensing would then be required.

Additionally, Oracle reminds us that the mere presence of an entry in DBA_FEATURE_USAGE_STATISTICS does not necessarily imply a licensing obligation. To quote the same document further:

“Licensing is based on feature usage, not just the presence of a single entry in DBA_FEATURE_USAGE_STATISTICS”*

Analogous situations occur, for example, in the Oracle Enterprise Manager Cloud Control environment, where the SYSMAN schema also uses ACO, even though the product itself does not require separate licensing of this option.

„Advanced Compression Feature being used for SYSMAN schema even though Not Licensed” (Doc ID 1458652.1)”*

From an administrative and licensing perspective, it is important to know that some database functions are used automatically by Oracle applications – not because they have been explicitly enabled by the user, but because they result from the default mechanisms of these applications. Attempt to modify such objects yourself (e.g. disabling compression in RCU columns) is not recommended – it can lead to unpredictable consequences of the system.

Author: Karol Kaleta, IT Consultant, Red Stack Poland

* Data comes from correspondence between Red Stack Poland and the Oracle support team at My Oracle Support (MOS) as part of a service request (SR).