Home
Welcome to the HCL Domino 11.0.1 documentation
Welcome to the HCL Domino® 11.0.1 documentation. Here administrators can find information about planning, installing, configuring, and administering Domino 11.0.1.
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.
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.
Detecting corrupted databases
You can identify corrupt databases without bringing down the Domino® server. In some cases, the cause of database corruption may be determined by examining the database in the corrupt state.

Welcome to the HCL Domino 11.0.1 documentation
Welcome to the HCL Domino® 11.0.1 documentation. Here administrators can find information about planning, installing, configuring, and administering Domino 11.0.1.
- Translated documentation
  The HCL Domino 11.0.1 documentation is currently available in the following languages.
- What's new in Domino® 11?
  Learn about all of the new features for administrators in HCL Domino® 11.
- Overview
  Welcome to HCL Domino® Administrator Help.
- Domino trial
  A trial version of HCL Domino® 11.0.1 is available free of charge.
- Installing
  Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
- Planning
  Use this topic as an overview of planning task.
- Configuring
  Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
- Securing
  This section describes security features, including execution control lists, IDs, and SSL.
- 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.
    - 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.
      - Detecting corrupted databases
        You can identify corrupt databases without bringing down the Domino® server. In some cases, the cause of database corruption may be determined by examining the database in the corrupt state.
        Collecting corruption data for all databases on a server
        The automatic detection and collection of corrupted database occurs at database open. The automatic facility will collect any database detected to have corruption within the configuration parameters currently active.
        Capturing corruption data for a specific database
        The dbcapture tool is provided as a standalone tool to collect a specific database manually at the discretion of the administrator or user.
      - Using Fixup
        When you restart a server, the server quickly searches for any unlogged databases that were modified but improperly closed because of a server failure, power failure, hardware failure, and so on. A few minutes after server startup is complete, the Fixup task then runs on these databases to attempt to fix any inconsistencies that resulted from partially written operations caused by a failure.
      - Fixup options
        The information in this topic describes the options that are available when you run Fixup.
    - 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.
- Tuning
  Use this information to improve HCL Domino® server, Domino Web server, and messaging performance through the use of resource balancing and activity trends, Server.Load commands, advanced database properties, cluster statistics, and the Server Health Monitor.
- Troubleshooting
  This section describes how to find and solve problems with HCL Domino® server and Administrator client.
- Notices

Detecting corrupted databases

You can identify corrupt databases without bringing down the Domino® server. In some cases, the cause of database corruption may be determined by examining the database in the corrupt state.

About this task

When the Domino® server detects that a database has corruption, Domino® automatically stores the corrupted database as a separate file in a separate directory. You can enable and control the automatic collection of all corrupt databases by setting certain Domino® configuration variables. Or, you can capture corruption values manually for a specific database.

Databases will not be collected, automatically or with the dbcapture tool, in the following cases:

The DATABASE_CAPTURE_LIMIT has been reached.
Collecting the database would exceed the total size for collected databases as set in DATABASE_CAPTURE_SIZE_LIMIT.
The database has already been collected.
The database is being processed by the compact or fixup tasks.

Perform the following tasks: