Prevents Verity Spider from optimizing the collection, thus reducing processing overhead during indexing. Use this option sparingly, as it leaves the collection in less than optimum shape. The following are some examples of when you might want to use this option:

• You want to manually perform custom optimization of the collection, using the mkvdk utility. By default, the Verity Spider optimization mimics the mkvdk actions of maxmerge and vdbopt. For more information on the mkvdk utility, see Verity Command-Line Indexing Reference and Using the mkvdk utility.

• You are running multiple indexing jobs against a collection, and want to wait until they are all finished to optimize.

Generally, do not leave a collection unoptimized for too long, as search times can slow significantly.

In brief, optimizing a collection means creating a few large partitions, which can greatly reduce search times.

Deletes document tables and index files in the collection, and cleans up the collection's persistent store. The collection is then fresh with its original style files, and is not deleted from the file system.

Specifies a failure-recovery mode for the collection, where the goal is to determine the causes of any errors, repair the errors (if possible), and restart a collection.

Although the Verity indexing engine always leaves the collection in a consistent, usable state, and no data can be lost or corrupted because of computer failures, it is possible for a process or event external to the Verity server to corrupt one or more collections.

You can use the -repair option for constant failure-recovery operation, or you can run it selectively on collections that failed.