Thanks for the question, vishal.
Asked: November 18, 2017 - 7:23 pm UTC
Last updated: November 27, 2017 - 4:35 pm UTC
Version: 11g
Viewed 1000+ times
You Asked
Hi ,
We have implemented archival solution for a client and now exploring further actions. Initial data size was around 25 TB's with major tables partitioned monthly. After archival, the size of active DB is around 13 TB's and archival DB is around 12 TB's with growth of around 800 GB's every month.Archival is planned every quarter to archive 3 months of data. I have 2 questions to ask:
1. What are the effective ways to compress data in archival DB, considering major chunk of data is in BLOB. Assuming the compression is transparent to application with some hit on the performance, what options are available? can the options be applied per partitions for a certain table.
2. What after archival, after keeping data in archival DB for 5 yrs it may allowed to keep it offline. What is the best options and how fast can be retrieval if required?
Thanks,
and Chris said...
Is this answer out of date? If it is, please let us know via a Comment