You can use the wgn_roll_partitions procedure to purge a specific partition by setting the new_partition_date_range parameter to NULL. The prototype is shown below:
wgn_roll_partitions( new_partition_date_range IN VARCHAR2, date_range_to_purge IN VARCHAR2, db_type IN NUMBER );
Where:
Specifies the end date for the new partition.
This parameter adds the new partition into the existing tablespace. In the Wgn3PurgeHistory table, this date is listed in the P1 column.
By default, the date format must be dd-mmm-yyyy (for example, 08-mar-2011).
Specifies the end date for the partition that you want to purge. Date formats are as above.
This parameter purges all non‑permanent data from the partition specified by the date_range_to_purge parameter. In the Wgn3PurgeHistory table, this date is listed in the P2 column.
Specifies the database that you want to partition:
(Default) Specifies the CMS database tables.
Specifies the data warehouse tables.
Specifies both databases. That is, you want to partition tables in the CMS database and the data warehouse.
Note: When you purge a partition, the partition is not automatically deleted. For instructions on deleting a specific partition, see the reference below.
Example
This command purges a CMS partition with an end date of 31 January 2011:
EXEC wgn_partition_util.wgn_roll_partitions ( new_partition_date_range => null, date_range_to_purge => '31-jan-2011', db_type => Wgn_Partition_Util.wgn_db_type_CMS );
Copyright © 2014 CA.
All rights reserved.
|
|