Home
Administering
This documentation provides information about the administration tools for managing and monitoring servers and databases.
Managing databases
Topics in this section describe how to set up and manage Domino® databases.
Full-text indexes for single databases
You can create full-text indexes to allow users to quickly search for information in databases. To search in a database, users enter a word or phrase in the search bar of the database to locate all documents containing the word or phrase.
Creating and updating full-text indexes for single databases
As you create a full-text index for a database, select indexing options and update frequency options carefully, as they can affect server disk space and processing speed.
Setting a schedule for Updall in a Program document
When creating a full-text index for a single database, if you select the index update frequency option Scheduled, you must set up a Program document in the Domino® Directory to specify the schedule you want for the Updall server task.

Administering
This documentation provides information about the administration tools for managing and monitoring servers and databases.
- Administration tools
  Topics in this section describe the tools you can use to administer a Domino® server.
- Monitoring
  This section describes how to use the tools and features that help you monitor a Domino® system.
- Managing servers
  Manage Domino® servers by performing any of these tasks.
- Managing databases
  Topics in this section describe how to set up and manage Domino® databases.
  - Database design, management, and administration
    The tasks involved with application design, database design, database management, and Domino® system administration may overlap, depending on the size of your organization and the structure of job responsibilities. In some organizations, an application developer may be responsible for both application and database design, while in others, a database manager may handle all database design and management tasks. In addition, database management overlaps with Domino system administration.
  - Increase the document summary data limit to 16 MB
    You can increase the document summary data limit on Notes 9 databases to 16 MB.
  - Organizing databases on a server
    You can organize databases in folders.
  - Attachment consolidation
    The Domino® server employs the Domino Attachment and Object Service (DAOS) to save significant space at the file level by sharing data identified as identical between databases (applications) on the same server. Document attachments are the first components to use the DAOS feature in Domino.
  - Full-text indexes for single databases
    You can create full-text indexes to allow users to quickly search for information in databases. To search in a database, users enter a word or phrase in the search bar of the database to locate all documents containing the word or phrase.
    - Security and full-text indexes for single databases
      When you create a full-text index for a single database, selecting the option Index encrypted fields can compromise system security
    - Attachment full-text indexing
      The Domino® server and Notes® standard client use Apache Tika 1.18 open source conversion filters to extract text for full-text searches of attachments. Tika replaces the KeyView conversion filter used in previous releases.
    - Restricted field names in full-text indexing
      Some field names are not supported in full-text indexing.
    - Creating and updating full-text indexes for single databases
      As you create a full-text index for a database, select indexing options and update frequency options carefully, as they can affect server disk space and processing speed.
      - Setting a schedule for Updall in a Program document
        When creating a full-text index for a single database, if you select the index update frequency option Scheduled, you must set up a Program document in the Domino® Directory to specify the schedule you want for the Updall server task.
    - Changing update frequency of a full-text index
      If a database is already full-text indexed, you can change the existing frequency setting on the Full Text tab of the Database Properties box.
    - Manually updating full-text indexes for single databases
      You can use the Domino® Administrator to update indexes manually after new information or documents have been added to databases. You can update a single index in the Database Properties box, or update one or more indexes from the Tools pane.
    - Deleting full-text indexes for single databases
      Delete a full-text search index when you no longer need it, when you need to the change the index options, or when you discover problems with the index.
  - Database libraries
    You can create a database library that contains databases that pertain to a specific collection of users or to a specific topic. For example, a corporate database library might include all databases that deal with corporate policies and procedures, and a marketing database library might include databases that are useful to the marketing staff.
  - Database catalogs
    A database catalog provides a list of all databases on a server. You use the server Catalog task to create a database catalog. The Catalog task bases the catalog file (CATALOG.NSF) on the CATALOG.NTF template and adds the appropriate entries to the catalog's ACL.
  - The Files tab in the Domino® Administrator
    The Files tab in the Domino® Administrator provides an easy way for you to manage files in the Domino data folder.
  - Replicating unread marks
    Unread marks can be replicated for selected databases, most notably mail databases, by using the advanced database properties from the Domino® Administrator or from the database properties box. When you enable the replication of unread marks on mail databases, users can read their mail from a workstation on ServerA, and after replication, can read their mail from a workstation on ServerB, with unread mail clearly delineated from mail that has previously been read.
  - Using indirect files to run database maintenance tasks
    You can use indirect files to run the same maintenance task multiple times, resulting in significant time savings. The fixup, compact, updall, design and convert maintenance tasks support using indirect files. You can also create batch files or scripts that run several maintenance tasks serially against different indirect files to help complete them quickly. If you have multiple CPUs, you can run the same maintenance tasks against multiple indirect files so they run concurrently. It is recommended you only run as many concurrent maintenance tasks as you have CPUs, otherwise they will start competing for CPU resources and can take longer to complete.
  - Updating database indexes and views
    A view index is an internal filing system that Notes® uses to build the list of documents to display in a database view or folder.
  - Synchronizing databases with master templates
    To use a consistent design for multiple databases, database designers can associate databases or elements within databases with a master template.
  - Fixing corrupted databases
    Corrupted databases don't occur frequently when you use transaction logging. When you use transaction logging to log changes to databases, a server automatically uses the transaction log to restore and recover databases after a system failure -- for example, after server failures or power failures. If a disk failure occurs, you use the transaction log along with a certified backup utility to restore and recover the databases.
  - Moving databases
    It may be necessary to move a database from one server to another -- for example, to distribute databases evenly among servers. If there are replicas of the database, the server to which you move the database should have the appropriate Connection documents to replicate the database to other servers that store replicas. If you're moving a database to a server in a cluster, replication between the server and other servers in the cluster that have replicas of the database occurs without Connection documents.
  - Using load convert to convert non-mail databases
    You can use the server's mail convert utility to convert non-mail databases to another type of non-mail database. Non-mail databases are all databases that do not have a $Inbox folder.
  - Redirecting client references to databases
    You can redirect Notes® client references from deleted or moved databases to a database replica that you specify.
  - Running a database analysis
    A database analysis reveals changes in documents, user activity, and other details such as replication data.

Setting a schedule for Updall in a Program document

When creating a full-text index for a single database, if you select the index update frequency option Scheduled, you must set up a Program document in the Domino® Directory to specify the schedule you want for the Updall server task.

Procedure

From the Domino® Administrator, click the Configuration tab and expand the Server section.
Click Programs.
Create or edit a Program document.
On the Basics tab:
1. Type Updall in the Program name box.
2. Type any optional arguments in the Command line box.
3. In the Server to run on box, enter either the full hierarchical name of a server on which Updall should run, or an asterisk (*) to run the task on all servers.
  Note: Qualified wildcards and group names are invalid in this field.
On the Schedule tab:
1. Select Enabled.
2. Select the time for Updall to update the index in the Run at times box.
3. Select a repeat interval, if any, in the Repeat interval of box.
4. Select the days of the week for Updall to update the index in the Days of week box.
Save and close the Program document.