Content Server Running in a Cluster: New Content Is Not Being Indexed
Last updated on DECEMBER 15, 2017
Applies to:Oracle WebCenter Content - Version 10.1.3.3.2 to 10.1.3.5.0 [Release 10gR3]
Information in this document applies to any platform.
You are running Content Server in a cluster. New content that is checked in to Content Server is not getting indexed. It looks like the Automatic Update Cycle of Indexer is Locked.
You have removed all of the lock files (other than lockwait.dat) from the <Content_Server>/search/lock directory and restarted all of the cluster nodes.
When you look at the Indexer tab of Repository Manager, it shows a State of Active with other fields listed as "unknown". If you try to Cancel the Update Cycle, it seems to just hang.
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