Before you configure a Database -- Compact probe or Database -- Design probe, make sure that you are familiar with the Compact task and with updating database designs.

For more information about using the Compact task, see the topics Compacting databases and Compact options.

For more information about refreshing or replacing the design of a template, see the topic Upgrading to a new Domino Directory template. The procedure described in the topic uses the Domino directory (PUBNAMES.NTF) as the example, you can apply the same procedure to other templates.

When configuring the Database -- Error Monitoring probe, use the Errors to ignore field to specify errors that the probe should ignore. This probe provides visibility to unusual NSF and NIF errors on local servers. When this probe is enabled, and an error is encountered, the error code is checked against an "Errors to ignore" list. If the error code is on the list, no further action is taken. If the error is not on the list, a DDM event is generated. The event identifies the operation that failed, the issuing server, the database name, and the specific error code. DDM automatically appends information that pertains to the error code, such as the probable cause and corrective action, if any.

This table contains the names and descriptions of the Database probes that you can define. For information about configuring the Database probes, see the topic Creating Database probes.

Database probe name	Description
Database -- Compact	Reports errors that occur when a database is compacted.
Database -- Design	Reports errors that occur when the design of a database is updated.
Database -- Error monitoring	Monitors key APIs in NSF and NIF, which are used to perform database operations and generates events for errors that occur.
Database -- Scheduled Checks	Reports if the named database cannot be opened. The probe can also check for unused space in the database and for database inactivity.

See also

Maintaining DDM Probes
Deleting a DDM Probe document
DDM probes

Glossary