Last updated on JULY 05, 2017
Applies to:Oracle Knowledge - Version 8.2.3 and later
Information in this document applies to any platform.
There are times when resetting the content store database (the database used by the indexer for crawl processing) may be necessary. Two of these times are if crawl performance has gradually degraded in a way you suspect that the database may be having issues (this could be indicated by the DBA), or there have been errors in the crawl that you cant recover from.
The steps to reset the contentstore database are listed below.
Note: While in general you should not have to reset revisions to reset the content store database, when there have been error conditions during a crawl it could be necessary to also reset the revisions. This will require a brief downtime for the runtimes to also reset the revisions there.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms