Manage regular maintenance tasks

Periodically, a set of maintenance tasks are executed. These tasks concern database organization and partition lifecycle management.

The best practice is to schedule a maintenance execution at least once a week. Maintenance tasks can be executed on demand. It is possible to execute all maintenance tasks when the task parameter is omitted. You can also execute specific tasks such as:

dstools maintenance -timeout 60

The timeout parameter is used to limit maintenance task execution to a predefined maintenance window. When the timeout occurs, the system continues with the next maintenance execution.

Purge expired information

Most of Datastore's query results are cached using dedicated database objects.

The query results expire when the lifetime set during the query definition ends.

When a query result expires, it must be removed from the database using the maintenance task: CLEAN_CACHE_ENTRIES

To purge expired information, execute the following maintenance task periodically: dstools -maintenance -tasks CLEAN_CACHE_ENTRIES

Note   A timeout parameter can be used to adjust the execution time to the maintenance window.

The maintenance task drops a query cache table after a waiting period defined by the AdminGUI / Deprecated cache retention period parameter.

Purge wrong information

When the injection fails, injected information is stored in the database but cannot be reached by queries. This wrong information must be purged to release the corresponding allocations.

To purge wrong information, execute the following maintenance task: dstools -maintenance -tasks CLEAN_COLLECTION

Note   A timeout parameter can be used to adjust the execution time to the maintenance window.

See also Use the Datastore Runtime command tool and Partition lifecycle management.

Related Links