Previous Topic: Retrospective PartitioningNext Topic: Partitioning an Existing Data Warehouse (Oracle)

Database Guide › Database Storage and Partitioning › Set Up Partitions and Purging › Retrospective Partitioning › Partitioning an Existing CMS Database (Oracle)

Partitioning an Existing CMS Database (Oracle)

The following command partitions the CMS database with partition dates that match the CMS.

Run this command as the schema owner, using the SQL*Plus utility:

SQL> EXEC Wgn_Partition_Util.wgn_partition_tables(
	partition_dates 		=> Wgn_Partition_Util.get_partition_dates(Wgn_Partition_Util.wgn_db_type_cms)
	, db_type 		=> Wgn_Partition_Util.wgn_db_type_cms
	, Partition_Options 	=> Wgn_Partition_Util.wgn_opt_Convert_to_Partitioned
	, new_tablespace 	=> 'WGNDATA'
	, new_indextablespace 	=> 'WGNDATAIDX'
	, pdebug 		=> True 
	);

This command converts the following tables to partitioned tables and migrates the data:

CMS Event Tables

Other CMS Tables

The following tables and indexes are placed in the default tablespace. The database administrator can move these tables and indexes to a more suitable location:

Sample scripts to convert and move the CMS database are available from CA Support.