Performance Best Practices for Purge

These are some of the best practices to follow when you use Purge:

Create or alter indexes on MATCHRESULTDETAILS, MATCHCANDIDATE_PTIDX1, MATCHCANDIDATEDETAILS_PTIDX1, MERGERESULT_PTIDX1, PRODUCTSTATUS, PRODUCTKEY, ACTIVITYRESULT and RELATIONSHIPDEFINITION tables.
Contact TIBCO Engineering team for the indexes scripts.
Resize the redo logs depending on the analysis of Automatic Workload Repository (AWR) reports. Consider resizing the redo logs based on the Redo Size in AWR and the redo interval. Consider increasing the size of redo logs and also the number of redo logs.
Log file switch: for a 10 minute switch, the total redo log file size should be approximately 2.5 GB. This enables the log switch to occur in 12 to 15 minutes.
- Use the AWR report: Report Summary to calculate the required size.
- Check Load Profile: Redo Size and take the per second size and calculate the required size for 12-15 minutes.
- Next, check the assigned redo logs. You can increase the size of the logs and number of logs. If the log file size is too large, the switch does not occur for some time and delays data recovery and the data being written. If there are too many log files, multiple concurrent accesses are supported but switches still occur.
- Consider moving the redo logs to faster disks to avoid log file switch delays.
- Set the size of the System Global Area (SGA) in Oracle, based on the recommendations in Automatic Database Diagnostic Monitor (ADDM) reports.