You manually update the search index if you change the search analyzer, if you create a Model Repository Service to use existing repository content, if you upgrade the Model Repository Service, or if the search index files become corrupted. For example, search index files can become corrupted due to insufficient disk space in the search index root directory.
The amount of time needed to re-index depends on the number of objects in the Model repository. During the re-indexing process, design-time objects in the Model repository are read-only.
Users in the Developer tool and Analyst tool can view design-time objects but cannot edit or create design-time objects.
If you re-index after changing the search analyzer, users can perform searches on the existing index while the re-indexing process runs. When the re-indexing process completes, any subsequent user search request uses the new index.
To correct corrupted search index files, you must delete, create, and then re-index the search index. When you delete and create a search index, users cannot perform a search until the re-indexing process finishes.
You might want to manually update the search index files during a time when most users are not logged in.
In the Administrator tool, click the
Manage
tab >
Services and Nodes
view.
In the Domain Navigator, select the Model Repository Service.
To re-index after changing the search analyzer, creating the Model Repository Service to use existing repository content, or upgrading the Model Repository Service, click
Actions > Search Index
Re-Index
on the
Manage
tab
Actions
menu.
To correct corrupted search index files, complete the following steps on the