Are there any special considerations in using advanced compression under an EBS database? We are currently on 10.2.0.4 but we will be moving to 11gR2 shortly.
I assume that it should be agnostic to the database usage, but I haven't seen any discussion on this yet.
We are approaching over 250gb so we are looking at this solution. Currently we are connected to a SAN.
Also: would it really make a difference as to when we implement advanced compression (ie: during an 11gR2 upgrade, or after)?
Edited by: user469492 on Jul 12, 2010 10:06 AM
Here is what I would suggest.
1 Start with Index compression first
2 Pick few largest indexes and compress them
3 Test the application for any anomalies
4 Pick few more Indexes and compress them
6 Start table compression with few biggest tables
I used similar method during the compression in our environment.
Your database size is not too large so you are in good shape and in better position to start the compression.
Hope this helps.
Pl also see these links
Pl make sure that you are licensed appropriately to use this feature.