Redefinition For Move Tablespace.

Question

Hi,
   I am using Release 11.2.0.3.0 of oracle. Now i am supposed to move a 'big table big_tab1(~700GB)+its indexes' to a different tablespace which is encrypted. I am trying to follow redefinition approach inspite of ALTER TABLE MOVE , as because we wont be able to have much downtime on prod. But below are my difficulties.
   I am having a foreign key constraint(con_1) on table tab1 which refers to the primary key of big table  big_tab1. if i am using COPY_TABLE_DEPENDENTS for copying all the constraints and indexes as it is, then all my indexes not being shifted to encrypted tablespace, they are created in the existing unencrypted tablespace only?
                                                                         else
   If i am creating the indexes/constraints manually (by specifing the encrypted tablespace) on the interim table, just after the START_REDEF_TABLE, then my indexeses will be created on new encrypted tablespace but i have to drop the existing foreign key(con_1) and create the 'foreign key constraint ' that is on table tab1, and it will refer to the redefined table big_tab1, so it will take lock for that duration of ALTER statement, and the purpose of online redefinitio will not be full filled.
   Please suggest?

Answer 1

You are confused.
The data for a table is stored in segments. For a partitioned table the data is contained in partitions: the table HAS NO DATA. Each partitions data is stored in its own segment which can be in its own tablespace.
For a subpartitioned table the data is contained in subpartitions: the table HAS NO DATA, the partitions HAVE NO DATA. ALL DATA IS IN THE SUBPARTITIONS. Each subpartitions data can be in its own tablespace. There is NO index data to be moved. There is NO index partition data to be moved. There is NO data except the data in the index subpartitions.
If you want to modify the tablespace the NEW partitions or subpartitions will use (as opposed to moving existing data to a new tablespace) then you need to use the 'modify_index_default_attrs' clause of the ALTER INDEX statement.
See ALTER INDEX in the SQL Reference
http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_1008.htm#BGECEJHE
>
modify_index_default_attrs
Specify new values for the default attributes of a partitioned index.
Restriction on Modifying Partition Default Attributes The only attribute you can specify for a hash-partitioned global index or for an index on a hash-partitioned or composite-partitioned table is TABLESPACE.
TABLESPACE Specify the default tablespace for new partitions of an index or subpartitions of an index partition.
>
See the example in the doc
>
Modifying Default Attributes: Example The following statement alters the default attributes of local partitioned index prod_idx, which was created in "Creating an Index on a Hash-Partitioned Table: Example". Partitions added in the future will use 5 initial transaction entries and an incremental extent of 100K:
ALTER INDEX prod_idx
MODIFY DEFAULT ATTRIBUTES INITRANS 5 STORAGE (NEXT 100K);