11g WCC - What Happens During a Fast Rebuild When Using OracleTextSearch? (Doc ID 1665323.1)

Last updated on AUGUST 09, 2017

Applies to:

Oracle WebCenter Content - Version 11.1.1.5.0 and later
Information in this document applies to any platform.

Goal

A rebuild of the search index can be done in the 11g Webcenter Content server without having to rebuild the entire "collection" in the Repository Manager.  Using Oracle Database 11g (which comes with Oracle Text enhancements), an index rebuild does not require doing a full Collection Rebuild.

This is different from doing a Full Collection Rebuild in Repository Manager.  With a Collection Rebuild, the full text indexing table (IdcText1 or IdcText2, depending which is the currently inactive index) is dropped and re-created.  With a Fast Rebuild, only the index on the table that is the currently active index is re-created.  A full Collection Rebuild drops the inactive table and its indexes and re-creates the table and its indexes.  A Collection Rebuild then goes on to perform a text extraction on every released content item checked into WCC and inserts the blob of extracted text into the table, which triggers the indexes to be updated. The Collection Rebuild process is much more lengthy since it requires touching every document for text extract, as well as inserting the metadata into the IdcText1 or IdcText2 table. 

 

By default, a Fast Rebuild uses the existing active index table and index, and disrupts checkins from getting released until it is finished. This is for best performance and fastest rebuild time. However, it is recognized that large installations could have a fast rebuild which takes hours or even days. New checkins are a part of the running business and so it may be necessary to sacrifice a little performance in the fast rebuild but allow new checkins to be processed and released as usual. To do this, you need to add the following setting in your configuration file (config.cfg, or the Configuration Manager under Admin Server):

AllowConcurrentUpdate=true

You will need to restart the server for the setting to take effect.


In addition the Fast Rebuild will drop and recreate the section group and re-add the metadata fields that are designated to be optimized (as in an SDATA section) or zoned indexes (as in a ZONE section).

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms