DBMaintenance Utility


Overview

Using DBMaintenance Utility

Recommended Usage

Examples


Overview

DBMaintenance utility can be used to perform the following maintenance tasks on the CommServe database:


Using DBMaintenance Utility

This utility is located at <Software Installation Path>/Base directory. From the command prompt, run dbmaintenance with appropriate parameters from the list of available parameters. Running the utility without any parameters will give the complete list of supported parameters.

The CommCell services must be stopped before performing database maintenance.

Connection Parameters

The database instance and the logon credentials can be provided in the following optional connection parameters:

If this utility is run on a CommServe without any of the above mentioned connection parameters, the database instance will be automatically detected, and the logon information will be retrieved from the encrypted data in the registry.

Maintenance Parameters

The following maintenance parameters are available:

Custom Maintenance Parameters

Instead of the two maintenance schedules outlined above (full and recommended), it is also possible to specify the type of maintenance from the custom maintenance parameters given below.

The following custom maintenance parameters are available:

Shrinking the database is not recommended on a regular basis. For this reason do not perform a full maintenance regularly. If you would like to reindex all tables, use the reindexall option. Combining the reindexall with the checkdb option will have desired effect.
  • Only perform a shrinkdb if a lot of free space has become available, or it has been a long time since the last maintenance.
  • Please note that database maintenance can take half an hour or even longer to execute depending on database size.

Troubleshooting Parameters

The following options can be used to troubleshoot the database:


Recommended Usage

Review the following recommendations before using this utility:


Examples

The following examples explain the usage of this command in different scenarios: