Scheduling maintenance programs

Most maintenance programs should run when no other programs are updating the database or need exclusive access to the database. For example, you should not load data (ADDRPTOND, STRMONOND, arsload, arsdoc add ) at the same time that you run the disk storage maintenance command (STRDSMOND).

However, the STRASMOND command can be run while archiving data into Content Manager OnDemand. Backups should not be run while STRDSMOND, STRASMOND, or loading of data are running. The time of day and frequency with which you run the maintenance commands and the processing options that you specify will vary, based on your environment.

For example, if you do not load data every day or you add few rows to the database when you do load data, then you should be able to schedule maintenance less often, perhaps once a week. However, if you load a high volume of data every day, then you should maintain the database after the load processing completes. If your system has plenty of disk space available to store index data and reports, then you might be able to schedule the maintenance programs less often.

The examples that follow illustrate one method of daily maintenance. The examples use the typical options to maintain the database and disk storage and take full backup images of the databases. The maintenance programs are scheduled to run early in the morning, before users begin accessing the system. Such a schedule would assume that all data loading completed before the maintenance programs begin. You should use the examples as a guideline.