This chapter focuses on database purges driven by the CA DataMinder infrastructure. That is, the scheduled purges are configured in the machine policy; the infrastructure then invokes the relevant database stored procedures (SPs). This contrasts with the partition-based purges described in 'Set up partition-based purging'.
However, a purging strategy for a partitioned database will typically require both. This is because partition-based purging will drop individual partitions but not the corresponding blob files. You must therefore schedule infrastructure-based purges to delete the residual blobs, using a custom ‘no operation’ SP to prevent these purges from trying to delete database records that may have been already removed by a partition-based purge.
Important! Infrastructure-based purging is not suitable for high volume Oracle CMS installations. You must use partition-based purges on these CMSs.
|
Copyright © 2014 CA.
All rights reserved.
|
|