28.1 Analyzing and Fixing Databases for Libraries and Documents

For libraries, the Analyze/Fix Databases option of Mailbox/Library Maintenance looks for problems and errors in library and document databases and then fixes them if you select the Fix Problems option.

  1. In ConsoleOne®, browse to and select one or more Library objects.

  2. Click Tools > GroupWise Utilities > Mailbox/Library Maintenance.

    Mailbox/Library Maintenance dialog box

  3. From the Action drop-down menu, select Analyze/Fix Databases.

  4. Select from the following options:

    Structure: When a user experiences a problem that is related to the library databases, you should perform a structure check. The structure check verifies the integrity of the databases and reports the amount of space that could be recovered. If there is a structural problem, the databases are rebuilt with free space reclaimed.

    Index Check: If you select Structure, you can also select Index Check. An index check can be time-consuming.

    Contents: The library database (located in the gwdms directory of the post office) does not contain documents. Documents are stored in the lib0000-FF directories. A contents check analyzes references from libraries to documents.

    Collect Statistics: If you selected Contents, the Collect Statistics option is available to collect and display statistics about the library, such as the number and size of documents.

    Fix Problems: This option tells Mailbox/Library Maintenance to fix any problems it finds. Otherwise, Mailbox/Library Maintenance just reports the problems.

  5. Using the tabs at the bottom of the Mailbox/Library Maintenance dialog box, set the following options:

    Selected options can be saved for repeated use. See Saving Mailbox/Library Maintenance Options.

  6. Click Run to perform the Analyze/Fix Databases operation on the library.

Analyze/Fix Databases can also be run using the standalone GroupWise Check program. See Section 34.1, GroupWise Check. It can also be scheduled to run on a regular basis by properly configuring the POA. See Section 36.4.1, Scheduling Database Maintenance.