IBM FileNet P8, Version 5.2.1            

Fixing an out-of-sync full-text index

A full-text index that is out of sync with the data in the object store database can cause your queries to give incorrect search results. You can submit an index job to resync the index.

Before you begin

Database indexes for index jobs. Create the appropriate database indexes to optimize index job performance.

About this task

An out-of-sync condition can occur, for example, if you restore a full-text index from a backup. The restored index is out of sync for the following types of objects:
  • Objects that were created, deleted, or moved to a different index after the backup
  • Objects that were modified after the backup

Before the resync index job begins, the resource status for the full-text index is OPEN, CLOSED, or some other initial status. If the initial status is CLOSED, the resource status remains CLOSED while the index job runs and after it completes. For all other initial statuses, some change occurs; in particular, the resource status is set to OPEN after the index job completes. While the index job is running, the resource status is set to CLOSED unless the initial status is UNAVAILABLE.

Procedure

To resync a full-text index:

  1. Access the index tab in the administration console:
    1. In the domain navigation pane, click the object store.
    2. In the object store navigation pane, expand the Administrative > Index Areas folder and click the index area that contains the index.
    3. In the details pane, click the Index tab.
  2. On the index tab, select the index in the Index selection field.
  3. Click the Resync button. A Resync Index Job window opens.
  4. In the Resync Index Job window, specify a resync modification date. Doing so causes the index job to reindex those objects that were modified after the specific date.
    Important: If you do not specify a resync modification date, the index job reindexes a fewer number of objects: namely, only those objects were created, deleted, or moved to a different index.
  5. Click Ok. An index job is created to resync the full-text index.
    Important: Do not set the resource status of the index to UNAVAILABLE after the index job starts. Doing so causes the index job to terminate without completing the resynchronization.
  6. Optional: Listing index jobs. Monitor the progress of the index job.


Last updated: October 2015
p8pcc212.htm

© Copyright IBM Corporation 2015.