IBM FileNet P8, Version 5.2.1            

Full-text index replacement

Some index jobs replace an entire full-text index with a new index. This manner of proceeding is faster than updating the current full-text index if all the objects with index entries in the current index need to be reindexed.

The following types of index jobs replace an index:

Such index jobs set the following property values automatically:

Property New index value Current® index value
Indexing status NORMAL REPLACING
Resource status OPEN CLOSED or UNAVAILABLE

Before the index job begins, the resource status for the current full-text index is OPEN, CLOSED, or some other initial status. While the index job is running, the resource status for the current index is set to CLOSED unless the initial status is UNAVAILABLE. Typically, you set the status to UNAVAILABLE if you suspect the full-text index to be corrupt.

Duplicate index entries

While the current full-text index is being replaced, an object might have two index entries: one entry in the current index and another entry in the new index. As shown in the following table, the effect of these duplicate entries depends on the resource status of the current index. These effects continue until the duplicate entries are removed when the index job completes (because the current index is deleted and replaced by the new index). If, however, you cancel the index job, the duplicate entries remain in existence until you submit another index job that replaces the current index.

Status Possible effect Description
UNAVAILABLE No effect Duplicate index entries have no effect because search servers ignore a full-text index with this status.
CLOSED Slower queries Duplicate index entries might slow search performance because duplicate results must be removed from the search results.
Fewer results for non-continuable queries Duplicate index entries might cause fewer search results to be returned for a non-continuable query for the following reason: a non-continuable query returns a limited number of search results and the duplicate entries count towards this limited number.


Last updated: October 2015
csscbr_index_rebuild.htm

© Copyright IBM Corporation 2015.