This content has been marked as final. Show 2 replies
1 person found this helpful
877938 wrote:The compression ratio will be unaffected since it is determined by the data itself and not where it is stored. Where you may feel the affects is with the slower IOPS of your new high capacity disks.
In this case, would there be any impact on the compression ratio as the expansion rack is having high capacity disks.
And, moving partition method would be same as it is for non-exadata database i.e. "alter table <table_name> move partition <partition_name> tablespace <tablespace_name>"Correct, unless it is possible for you to use transportable tablespaces. That would most likely be preferred. If that won't work for your environment, a couple of things to keep in mind, was the compression configured at the tablespace, table, or partition level? You want to make sure your compression intentions are persisted as you move to the new tablespaces.
And don't forget your indexes :)
Compression ratio will not be affected because of the high capacity disks(The indvidual disks are 2tb*12 running at a much lower RPM 7.2k)