Improving system performance by using the Data Cleanup utility
The Data Cleanup utility does not run on archived forms.
Watch the following video (2:15) to understand the overview of the Data Cleanup utility:
To update out-of-the-box settings for the Data Cleanup utility
An administrator uses the AR System: Stale Data Cleanup form to update the list of out-of-the-box forms and record definitions:
- To update out-of-the-box forms, open the AR System: Stale Data Cleanup form through Mid Tier.
- In Form Name, update the forms and record definitions.
The Form Name shows the default list of forms and record definitions where the Data Cleanup utility runs. - In Keep Days, update the age of data kept in forms and record definitions.
- In Timeout in Minutes, specify how long the Data Cleanup utility runs on a form.
Default —120 minutes.- You can configure different timeouts for different forms and record definitions.
- The timeout mentioned for the forms or record definitions must be less than the timeout you specify for the Data Cleanup utility.
For example, if the Data Cleanup utility timeout is 120 minutes, the form or record definition timeout must be less than 120 minutes.
- In Enable Form, select an option to enable the Data Cleanup utility to run on selected forms and record definitions.
Valid values:- Yes—Run the Data Cleanup utility for the forms selected in the Form Name field.
- No—Do not run the Data Cleanup utility for the forms selected in the Form Name field.
- In Form Name, update the forms and record definitions.
In the Centralized Configuration, update the default value of the Stale-Data-Cleanup-Cron-Job-Schedule setting.
For information about setting up a Cron job see, New in Spring 5.3: Improved Cron Expressions in spring documentation.
For information about scheduling a Cron job see, CronMaker application.
The Data Cleanup utility run is scheduled.
Considerations for running the Data Cleanup utility on the historic_process_context form
Consider the following points when you run the Data Cleanup utility on the historic_process_context form:
- You can delete the out-of-the-box record definitions only if the historic process context is enabled. For more information, see Disabling history of process instances.
- If child forms are disabled, the Data Cleanup utility does not delete records from the parent form.
- If timeout occurs for the child form, the Data Cleanup utility does not delete records from the parent form.
- All entries in the historic_process_context form are deleted if the following conditions are true:
- The historic process context is disabled.
- The form create date is lesser than the value in the Keep days field of the Stale Data Cleanup form.
List of out-of-the-box forms and record definitions
By default, the Data Cleanup utility runs on the following forms and record definitions:
Form name | Age of data for cleanup |
---|---|
ACT_GE_BYTEARRAY | 30 |
ACT_HI_ACTINST | 30 |
ACT_HI_ATTACHMENT | 30 |
ACT_HI_COMMENT | 30 |
ACT_HI_DETAIL | 30 |
ACT_HI_IDENTITYLINK | 30 |
ACT_HI_PROCINST | 30 |
ACT_HI_TASKINST | 30 |
ACT_HI_VARINST | 30 |
AR System Email Error Logs | 30 |
AR System Webhook Pending Error | 30 |
ASI:SYSAction | 30 |
CAI:EventParams | 30 |
CAI:Events | 30 |
CMDB:JobRunInfo | 7 |
com.bmc.dsm.notification-lib: Notification | 30 |
com.bmc.dsm.notification-lib: NotificationLog | 30 |
com.bmc.dsm.shared-services-lib: Application Error Details | 30 |
com.bmc.dsm.shared-services-lib: Automated status Transition Data Management | 60 |
com.bmc.dsom.ai-foundation-service-lib: Possible Major Incident Notification | 30 |
ES_Chat:Report_Event | 30 |
HISTORIC_PROCESS_CONTEXT | 30 |
HISTORIC_PROCESS_CONTEXT_ARCHI | 30 |
KPI:DataCollection | 365 |
NTE:Notifier | 30 |
Server Statistics: Longest SQLs | 30 |
SYS:Action | 30 |
SYS:Application Status Enabler | 30 |