Automatic Update Cycle is stuck in infinite loop. Content is indexed very slowly or not at all.
(Doc ID 2776186.1)
Last updated on MAY 20, 2021
Applies to:Oracle WebCenter Content - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 11g]
Information in this document applies to any platform.
Content items were getting indexed very slowly. Eventually, no content was getting indexed at all. As a result, large number of content items became stuck in Work In Progress page. No helpful errors were found in the UCM server logs, CS tracing, or CS system logs in Administration -> Log Files -> Content Server Logs.
Opened Repository Manager and it shows the Automatic Update Cycle is stuck in a loop between steps "Indexing additions" and "Loading web changes".
Please see below testcase (replicates the issue) for more information and symptoms about the issue.
NOTE: The illustrations below were taken from replicating the issue in a local test instance with an indexing batch of 1 and checkpoint of 5. The default values are 25 (batch) and 10000 (checkpoint). Therefore, the values seen in your environment will differ.
2. Create a folder. Then, load file test.txt several times (e.g., 10,000) into the same folder. The file will be renamed to "Copy of" as described in below KM Note.
NOTE: The checkin time will progressively take longer as more copies of the same file are loaded. This occurs because the same two queries are executed to see if the file (e.g., test.text, Copy of test.txt, or Copy(n) of test.txt) exists in the folder. This is explained in below KM note.
Loss Of Performance When Uploading Multiple Copies Of Same Content In A Folder (Doc ID 2773873.1)
3. Then, Automatic Update Cycle will begin indexing content slower than usual. Eventually, it will stop indexing any content. The content items in Work In Progress became stuck and the backlog just kept increasing as more content changes occur.
4. Opened Repository Manager to check on the indexer. Noticed that the Automatic Update Cycle just keeps running in a loop between steps “Indexing additions” and “Loading web changes”
Occasionally, the unknown status was displayed as well.
5. Set indexer verbose tracing in System Audit Information page to get more information about indexing these content items. Noticed the following trace entries were repeating for the same dID values.
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