When specifying a partition scheme, you can also specify the tablespace for an individual table or index object for the current session.
If you do not specify the tablespace for an individual object, CA DataMinder assigns tables to tablespaces in a specific order of precedence.
Example
The following Wgn_Partition_Util.Set_Obj_Tablespace commands specify:
SQL> EXEC Wgn_Partition_Util.Set_Obj_Tablespace('WGN3EVENT', 'TS_WGN3EVENT'); SQL> EXEC Wgn_Partition_Util.Set_Obj_Tablespace('IX_WGN3EVENT_EVENTTIMESTAMP', 'TS_IX_WGN3EVENT_EVENTTIMESTAMP'); SQL> EXEC Wgn_Partition_Util.wgn_partition_tables( date_range =>'31-jan-2010' , num_partitions =>12 , num_days_per_partition =>30 , db_type => Wgn_Partition_Util.wgn_db_type_CMS , Partition_Options => Wgn_Partition_Util.wgn_opt_Convert_to_Partitioned , new_tablespace => 'WGNDWTSF' , new_indextablespace => 'WGNDWTSFIDX' );
Tablespace Order of Precedence
CA DataMinder supports the following methods for assigning tables to tablespaces. CA DataMinder applies these methods in the following order of precedence:
If this function is used, the specified tablespaces override all other methods.
If custom tablespaces are used, they override the parameters in method 3.
new_tablespace new_Indextablespace parameters
If methods 1, 2 and 3 are not specified but a table is already assigned to a tablespace, CA DataMinder uses the existing tablespace.
CA DataMinder assigns a table to the default WGNDATA tablespace if no other sources are specified.
Copyright © 2014 CA.
All rights reserved.
|
|