User Guide
Table Of Contents
- Contents
- Introduction
- Administering ColdFusion MX 7
- Administering ColdFusion MX
- Using the ColdFusion MX Administrator
- Contents
- Initial administration tasks
- Accessing user assistance
- Server Settings section
- Data & Services section
- Debugging & Logging section
- Extensions section
- Event Gateways section
- Security section
- Packaging and Deployment section
- Enterprise Manager section
- Custom Extensions section
- Administrator API
- Data Source Management
- Contents
- About JDBC
- Adding data sources
- Connecting to DB2 Universal Database
- Connecting to Informix
- Connecting to Microsoft Access
- Connecting to Microsoft Access with Unicode
- Connecting to Microsoft SQL Server
- Connecting to MySQL
- Connecting to ODBC Socket
- Connecting to Oracle
- Connecting to other data sources
- Connecting to Sybase
- Connecting to JNDI data sources
- Web Server Management
- Deploying ColdFusion Applications
- Administering Security
- Using Multiple Server Instances
- Administering Verity
- Introducing Verity and Verity Tools
- Indexing Collections with Verity Spider
- Using Verity Utilities
- Contents
- Overview of Verity utilities
- Using the mkvdk utility
- Using the rck2 utility
- Using the rcvdk utility
- Using the didump utility
- Using the browse utility
- Using the merge utility
- Index

138 Chapter 9: Indexing Collections with Verity Spider
-purge
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.
-repair
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 due to machine failures, it is possible for a process or event
external to the Verity engine 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.
Setting MIME types
You can use the MIME type criteria options, -mimeinclude, -indmimeinclude, -mimeexclude,
and
-indmimeexclude, to include or exclude MIME types.
Syntax restrictions
When you specify MIME type criteria, keep in mind the restrictions described in the following
sections.
Using the wildcard character (*)
The asterisk (*) wildcard character does not operate as a regular expression for the value of the
MIME type criteria. Instead, you can only use it to replace the entire MIME type or MIME sub-
type.
For example, the following value is a valid substitute for text/html:
text/*
The following value is NOT a valid substitute for text/html:
text/h*
Multiple parameter values
When you specify a series of parameter values for a single instance of one of the MIME type
criteria, and you use-quotation marks, you must enclose each separate parameter value in single-
quotation marks. For example:
-mimeinclude ’text/plain’ ’application/*’
If you enclose the entire sequence of parameter values, as follows:
-mimeinclude ’text/plain application/*’
Verity Spider considers the entire expression a single value.