3.4 Tuning Data Archiving and Purging

Oracle BAM 12c recommends the following best practices for archiving and purging data.

  • Keep only the necessary data in your Data Object. Any data that is relevant for operational monitoring and taking actions is a candidate for data object storage.

  • Do not keep older data for historical purposes in the same data object. If you need the historical data to be available, transfer the data to another data object that is used for specific reporting.

  • Schedule the Data Retention at non-peak hours using alerts. You can shut down all BAM Viewsets and Continuous Queries if you’re an administrator during this task as they hold state in memory.

  • If it is a requirement to archive the data prior to purging, then use an Oracle Data Integrator service with BAM 12c.

  • Use alerts to control filter-based purging. Custom actions can also be provided to the alert to perform more customized purging.

  • Use the Database Partition capability to improve performance if purging and data injections are happening concurrently. For more information, see Partitioning Concepts in the Database VLDB and Partitioning Guide.