Scheduling the script-based cleanup job

You can set an execution schedule for the script-based cleanup job — the out-of-the-box BSA Recommended Database Cleanup Job or any other cleanup job that you created based on it — through the Schedules tab in the job editor of the open Network Shell Script Job.

You can schedule the cleanup job so it can run one time, recur hourly, daily, weekly, or monthly, or recur at some arbitrary interval, whichever time frame works best for your data cleanup strategy.

Tip

BMC offers the following recommendations for cleanup job schedules:

  • For a standard cleanup plan using the TYPICAL execution mode, a weekly run of the cleanup job should be sufficient.
    For an example of such a cleanup plan, see Example-weekly-database-cleanup-plan.
  • In a large operational environment where the database fills up quickly, or in situations where the database has accumulated large amounts of data and you need to catch up on database maintenance, your cleanup plan should include multiple jobs for individual cleanup modes that run more frequently (typically daily). For an example of such a cleanup plan, see Example-cleanup-plan-for-large-operational-environments.
  • Schedule a monthly cleanup of the agents and repeater server (cleanup jobs set to individual modes CLEAN_AGENT and CLEAN_REPEATER). For best results, keep the cleanup jobs for the agents and repeater server separate from your database cleanup jobs, as these jobs perform different actions and require more time to complete.
  • If you are using TYPICAL execution mode for the rest of your cleanup actions (the standard cleanup plan described above), schedule a monthly cleanup also for the Application Server caches (individual mode CLEAN_ALL_AS).

Note

When scheduling your cleanup jobs, avoid conflicts with other jobs:

  • If you use TrueSight Smart Reporting for Server Automation to create reports, be careful that cleanup jobs do not overlap ETL jobs for loading data to the reporting data warehouse. Typically, you first run the ETL job (to ensure that old data is available for reports) and only after the ETL job has finished you run the database cleanup job.
  • It is not recommended to run cleanup while running updates of database statistics (Oracle or SQL Server), so as not to impact the performance of the environment.

For a complete description of options, see Network-Shell-Script-Job-Schedules.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*