Re: Oracle License for Optional Packs Question
Date: Tue, 9 Jan 2018 11:40:43 +0530
Message-ID: <CAG6s0C32=pN6Gh6QSYkrVAksMOH_ysPimvPo28QUEsZrBDJftw_at_mail.gmail.com>
just like to know , Is it possible to restrict of using compression option
in export commands, because as said DBA's accidentally use it :) . With
the help of OEM is it possible to enable auditing or track the compression
usage ?
-Naga
On Sun, Nov 19, 2017 at 9:52 AM, Stefan Knecht <knecht.stefan_at_gmail.com>
wrote:
> The advanced compression option is extremely difficult to not accidentally
> use. It's literally everywhere:
>
> - Datapump export (but only if you compress the data, metadata-compression
> is "free")
> - Data Guard redo compression (which you can conveniently enable in the
> broker which may lead people to think it's a broker-feature and has nothing
> to do with the advanced compression option inside the database)
> - Securefile compression
> - Table & Index compression (this one is kinda obvious)
> - Flashback archives with OPTIMIZE DATA turned on
> - Heat map features in 12c
> - RMAN Backup compression (anything other than 'BASIC')
> - Online partition move (even to basic compression - this one is really
> evil)
> - ... and there's more: https://docs.oracle.com/
> database/122/DBLIC/Licensing-Information.htm#GUID-AB56CEE3-
> 955E-4E56-8B44-6075E889C283
>
>
> It's a really sneaky way of pushing this option into so many different
> things, and make it really easy to accidentally trigger it somewhere.
>
>
> --
> //
> zztat - The Next-Gen Oracle Performance Monitoring and Reaction Framework!
> Visit us at zztat.net | Support our Indiegogo campaign at igg.me/at/zztat
> | _at_zztat_oracle
>
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Jan 09 2018 - 07:10:43 CET