How To Do Metadata Searches While Rebuilding a Corrupted Index
(Doc ID 2237111.1)
Last updated on JULY 09, 2018
Applies to:Oracle WebCenter Content - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
When the WebCenter Content server is configured for ORACLETEXTSEARCH or DATABASE.FULLTEXT, although it should be rare, it can happen that the active index becomes corrupt.
The index is corrupted to the point that searches either outright fail (and generate an ORA or DRG error), or return incorrect results.
Items that should be returned in the search results aren't listed, items that shouldn't be returned in the search results are listed, or no items are returned.
When the active index is corrupt and requires a full collection rebuild, searches won't work until the index is completely rebuilt.
For small content repositories, this shouldn't be too much of an issue because the rebuild will at most take several hours.
However, for very large repositories (those in the millions) the time before the rebuild is complete may take several days or weeks.
This KM will provide steps to allow metadata searches to work while the rebuild is active.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|For searches from the WCC search page|
|For searches called from external applications|
|For soap requests|
|For RIDC requests|
|The way to verify that the metadata search is working|
|Once the index is rebuilt|