IMP Policy Evaluation
(Doc ID 2696440.1)
Last updated on SEPTEMBER 23, 2020
Applies to:Oracle Audit Vault and Database Firewall - Version 220.127.116.11 and later
Information in this document applies to any platform.
1) If you define a policy to compress data which has not been modified for a year, then it seems obvious that you have to wait a year to do so , However for existing large tables that is an issue . Knowing that 80% data has not been modified for year now based on modification date that is stored in the table. You want to compress it now to take the advantage of compression . Also you do not want to compress the segment entirely , the row/block based compression suits the table. Is there a way to achieve this?
2) Now you have seen that row/block level compression does not release the space back to OS, It is again an issue for large tables which have been growing over years, If lets say 80% compression ration is achieved by block level compression then it will take many years to fill up the space. Is there a way to release that space? Again if you use segment level compression it compress the recent data also which you may not want to compress as that can be updated. So how can this space saved be released?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document