(Oracle databases only)
Your database is now ready for you to implement partitions and a partition-based purging scheme. Specifically, you need to:
The CA DataMinder database schema provides support for table partitioning based on event time stamps. For example, you can set up 7 day or 30 day partitions.
Partition-based purging is dramatically faster than relying solely on infrastructure-based purging. After setting up partitions, you will need to configure the purging behavior. Typically, you will set up a purge strategy based on rolling partitions.
When you schedule or manually run a partition-based purge, your purge procedure must include steps to suspend the CMS and delete any corresponding blob files.
You can fully customize your partitioning and purging operations. For example, you can define the retention conditions for records due to be purged. You can also configure custom operations to run, for example, when a purge operation fails.
You can use functions in the wgn_partition_util package to specify the partition time ranges, create partitions, configure partition-based purging, and restart failed purges. You can customize the retention conditions and configure other custom operations using functions and procedures in the wgn_partition_cust package.
Copyright © 2014 CA.
All rights reserved.
|
|