Oracle datapump, advanced compression and licensing

1

As you may well know, Advanced Compression is an option you have to pay for when using it.

But as a DBA you can’t always control the use of this option, e.g. the use of Datapump with Compression parameters. Lately, a few customers were involved in a discussion with Oracle LMS (License Management Services) about the use of Advanced Compression within their database.

Using export scripts with the parameter  COMPRESSION=METADATA_ONLY (which is default) does not require the Advanced Compression option.

But when using the parameter COMPRESSION=ALL,the output of the LMS – scripts could be as this:

  
VERSION NAME CURRE LAST_USAGE_DATE LAST_SAMPLE_DATE FEATURE_INFO_       
----------------- ---------------------------------- ----- ----------------    -------------------  -------------------------------------------------------
 
11.2.0.4.0        Oracle Utility Datapump (Export)   TRUE   2014-12-17_23:22:32  2014-12-17_23:22:32 Oracle Utility Datapump (Export) invoked: 176 times, compression used: 63 times, encryption used: 0 times
 

It’s all about the phrase:  “ invoked: 176 times, compression used: 63 times

What can be concluded of this output:

  • It does say that Oracle Datapump was invoked and compression used, but not WHEN compression was used. It could be used in the first 63 times of the 176 times datapump was invoked. This is important because it shows that it wasn’t used deliberately, and the script was replaced in time e.g. When the compression used is close to 176, you’ve got a harder nut to crack.
  • If this is the only output which shows that you are using Advanced Compression, that is, no OLTP compression, RMAN, SecureFiles and Data Guard network compression, your defense is a lot stronger.
  • The fact that this option can’t be switched off seems quite a good case for a lawyer to crack. At this moment revoking users to use Data Pump at all is the only way to avoid its usage.
  • The fact that there’s an enhancement request to disallow unlicense compression feature with Datapump shows that there’s indeed a problem Oracle hasn’t been able to solve.
Bug 8478082 : DISALLOW UNLICENSED COMPRESSION FEATURE WHILE USING DATA PUMP

2 - Very desirable feature

*** 12/23/14 07:07 am RESPONSE ***
There is no way to disable the use of any of the features that are part of the Advanced Compression option. 
You can track the usage of those features with DBA_FEATURE_USAGE_STATISTICS, and if you discover a feature 
is being used when it shouldn't be, you can contact the user and ask them to stop using it.

So… when confronted with a license-incompliancy of Advanced Compression, purely based on the use of Datapump parameters, don’t take it for granted, but fight it.

Resources:

– Oracle doc about options and packs:  http://docs.oracle.com/cd/E11882_01/license.112/e47877/options.htm#DBLIC139

About Author

Job is a solution architect at AMIS Services with a special interest in Oracle licensing, High Availability architectures and managing complex (Oracle) environments, which includes Cloud environments.With a background as Oracle developer, DBA, team-manager and license-consultant he is able to utilize the Oracle technologies to a cost-efficient architecture for his customers.He is regularly involved in consultancy regarding: - Unlimited License Agreements (ULA). - License compliancy-checks and advice regarding optimizing the environment. - Second opinions. - Education / presentations about licensing and managing your infrastructure in the most cost-efficient manner.Twitter: @jobaclenl

1 Comment

  1. Sorry for my English, but i think it’s important to know what’s algorithm used by compression, because default behavior of expdp compression use the “NONE” Compression, that ‘s why you see a counter greater 0 on after “invoked”.
    If you see a value greater 0 after algorithm compression , indeed compresssion is used otherwise the compression is not used