Enable Database Scheduling

If any of the following messages are shown upon login or when typing health login, the steps below should be carried out:

• CACHE DATABASE MAINTENANCE NOT SCHEDULED
• TRANSACTION DATABASE MAINTENANCE NOT SCHEDULED

For general information on scheduling, see: Scheduling.

For considerations and guidance on frequency of the schedule to set up for your system. see the System Maintenance section of the Best Practices Guide.

Important

Schedules must be set up on all unified nodes. This ensures that they still run in the event of a failover and DR scenario.

• For cache database maintenance:

  With for example a schedule name dbcache:

  schedule add dbcache voss trim-cache

  See also Database Commands

  Typing health login at the command line will now not show the CACHE DATABASE MAINTENANCE NOT SCHEDULED message.

  The schedule instance can be modified, for example every 24 hours:

  schedule time dbcache every 24 hours

• For transaction database maintenance:

  With for example a schedule name dbtxn:

  schedule add dbtxn voss transaction archive 7

  or

  schedule add dbtxn voss transaction delete 7

  Note that transaction archiving also deletes transactions. For further details, see Database Commands for Transaction Management

  Typing health login at the command line will now not show the TRANSACTION DATABASE MAINTENANCE NOT SCHEDULED message.

  The schedule instance can be modified, for example weekly on Sunday:

  schedule time dbtxn weekly 0