Platform Deployment Guide › Content Services › Troubleshooting the Content Indexer › Documents Submitted to Content Database Time Out

Documents Submitted to Content Database Time Out

Symptom:

Documents that I submitted to the content database time out when I use the IDOL content connector.

Solution:

Timeouts occur when indexing a document into a content database takes longer than a preconfigured upper limit. Indexing can take longer, for example, because the document is large, or the server is too busy to index the document fast enough.

You can improve performance by performing one or all of the following solutions.

• Extend the index timeout limit.
  1. Edit the registry on the server hosting the IDOL connector framework and content database.
  2. Go to the following registry key:

     HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\CA DataMinder
         \CurrentVersion\Content Services\IDOL Provider
     

  3. Modify the IndexTimeoutMins registry value.

     Because content databases vary in size, we cannot give specific recommendations for the new timeout value. Investigate different timeouts until you discover the optimal timeout for your content database.

• Reduce the number of threads configured in the Content Indexer job. The default number of threads is 2 but you can specify values up to 26. Decrement the number of threads until you find the optimal value.
• Improve the performance of the IDOL server machine.
• Configure the Content Indexer job to generate EVL's on failure and re-ingest the failed events using a Retry Job at a quieter period.