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.
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.
Enabling and managing inline view indexing
A view index is an internal filing system that is used to build the list of documents to display in a database view or folder. By default, view indexes are updated on a server at scheduled intervals. To update a view index immediately after documents change instead, enable inline view indexing. When you enable inline view indexing, a critical view is always kept up-to-date for your users.
Setting index expiration for inline view indexes
Use NOTES.INI settings to control when inactive view indexes expire and are flushed out of memory.

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.
  - 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.
    - Indexer tasks: Update and Updall
      The Update and Updall tasks keep view indexes and full-text indexes up-to-date.
    - Maintaining databases using the dbmt tool instead of updall
      You can use the database maintenance (dbmt) tool for performing multiple daily/weekly administrative tasks on user's mail database files and other databases. The dbmt tool relieves the administrator of the need to run the Updall task.
    - Updall options
      The Updall task manages database view indexes and full-text indexes.
    - Keyboard shortcuts that update or rebuild views
      You can use keyboard shortcuts to update or build views.
    - Running multiple Update tasks
      To improve view indexing performance, you can run multiple Update tasks. Doing this can affect server performance and is recommended primarily for multi-processor machines. On a server with multiple processors, enable a maximum of one Update task per processor.
    - Dynamic indexing of high-usage views
      HCL Domino® can dynamically assign dedicated view indexing threads to views with content that is frequently updated. This feature keeps busy views up-to-date and enables them to be opened more quickly. You don't have to manually identify and manage view indexing for active views yourself.
    - Moving views out of databases
      You can move views out of Notes databases into separate view index files (.NDX files).
    - Enabling and managing inline view indexing
      A view index is an internal filing system that is used to build the list of documents to display in a database view or folder. By default, view indexes are updated on a server at scheduled intervals. To update a view index immediately after documents change instead, enable inline view indexing. When you enable inline view indexing, a critical view is always kept up-to-date for your users.
      - Enabling inline view indexing with the Updall task
        You can enable inline view indexing with the Updall task which updates the $Index view design element. With this method, inline view indexing is enabled automatically in replicas of a database. In addition, if you enable inline view indexing in a design template, the inline view indexing is enabled automatically in databases that inherit their design from the template.
      - Enabling inline view indexing with INLINE_VIEW_INDEX setting
        You can enable inline view indexing with the NOTES.INI setting INLINE_VIEW_INDEX. With this method, you specify a list of databases on a server to enable for inline view indexing. Unlike the Updall method, this method does not update the $Index view design element in databases and so does not propagate view indexing through replication and design inheritance.
      - Setting index expiration for inline view indexes
        Use NOTES.INI settings to control when inactive view indexes expire and are flushed out of memory.
      - Using console commands to manage inline view indexing
        Use server console commands to monitor and manage inline view indexing.
      - Showing inline indexing statistics
        Use the show stat database.inline* console command to show statistics about inline indexing on a server.
      - Disabling inline view indexing
        You can disable inline view indexing if you no longer want to use it. You can also temporarily disable inline view indexing to resolve a problem.
    - Purging view indexes
      Because a database grows when you add views and folders, you can improve database performance by occasionally purging view indexes from a database.
    - Changing the temporary folder used for view rebuilds
      When Domino® rebuilds views -- for example, when you use updall -R or when a user opens a view whose index has been deleted -- it may generate temporary files to sort the data in order to rapidly update the views; Domino deletes these files after rebuilding the views. By default, these temporary files are located in your system's temporary folder -- for example, C:\TEMP. If your system doesn't have a temporary folder, then Domino puts the files in the Domino data 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 index expiration for inline view indexes

Use NOTES.INI settings to control when inactive view indexes expire and are flushed out of memory.

About this task

Use NOTES.INI settings on a server to control when inline view indexes expire in:

inactive views in open databases
cached views in closed databases

Procedure

Use the settings described in the following table that correspond to the type of inline view index: design-enabled or static-enabled.

Tip: To determine whether an inline view index is static-enabled or design-enabled, use the show dbs * inline views command or the dbcache show inline views command. Look at the Type column in the output.

Table 1. Index expiration settings for inline view indexing
Setting	Description
`INLINE_VIEW_INDEX_DESIGN_ACCESS_MIN=<minutes>`	Open database view expiration for design-enabled inline indexes Default: no expiration.
`INLINE_VIEW_INDEX_STATIC_ACCESS_MIN=<minutes>`	Open database view expiration for static-enabled inline indexes Default: no expiration.
`INLINE_VIEW_INDEX_DESIGN_CACHE_MIN=<minutes>`	Closed database view expiration for design-enabled inline indexes Default: 5 minutes
`INLINE_VIEW_INDEX_STATIC_CACHE_MIN=<minutes>`	Closed database view expiration for static enabled inline indexes Default: 5 minutes