Hi Balaji ,
Do you see any reason why you are looking into compressing the tablespace . Are you in any sort of compulsion to reduce the disk usage ?
Compression more specifically should fall into a maintenance cycle and should not ideally fall during the implementation process .
As Yves has clearly suggested in his previous post , Compression do have benefits as well as it comes with a small percentage of performance degrade [ Performance may improve too ] especially during inserts / updates .
So it will be better served for you to think of compressing specific tables [ Involves decision on what tables to compress and why ] after Go-live [ When you see certain tables are growing significantly when compared to others and there is no CPU overhead in the systems ] .
In a nut shell , Do not compress if you are in no compulsion to reduce disk space [ Whish is the main benefit of compression ]
Compression let it fall during the maintenance cycle [ House keeping / Post go-live tasks ]
Thanks ,
Manu