10g UCM What Happens During a Fast Rebuild When Using OracleTextSearch? (Doc ID 960408.1)
Last updated on MAY 01, 2017
Oracle WebCenter Content - Version 10.1.3.3.0 to 10.1.3.5.0 [Release 10gR3] Information in this document applies to any platform.
***Checked for relevance on 01-Jun-2011***
A rebuild of the search index can be done in Universal Content Management (UCM) without having to rebuild the entire "collection" in the Repository Manager. Using Oracle Database 11g (which comes with Oracle Text enhancements) and UCM's OracleTextSearch component, 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) is dropped and re-created. With a Fast Rebuild, only the index on that table is re-created. A full Collection Rebuild drops the 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 UCM 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. A Fast Rebuild uses the existing table and index and does not disrupt user's checkins from getting released.
In Oracle Database 11g, a "shadow" text index can be created online in the database. This can be built while the original index is still in use, and when the index build is complete, the original index can be exchanged for the newly built shadow index. As soon as this process is completed, queries will automatically transition to the new index.
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