Platform Deployment Guide › Content Services › Troubleshooting the Content Indexer › IDOL server times out after upgrade

IDOL server times out after upgrade

Symptom:

After repairing or reinstalling the CA DataMinder IDOL Connector, my indexing job stalls and documents are timed out before they can be added to the content database.

The index.log file on the IDOL server contains repeated messages in this format:

"Database (<database name>) is readonly. Document <file name> not indexed."

Reason:

Timeouts occur when indexing a document into a content database takes longer than a preconfigured upper limit. In this case, the time-outs occur because the target database has been flagged as Read Only in the content.cfg configuration file. This change to content.cfg is caused by the following sequence of events:

1. When you repair or reinstall the CA DataMinder IDOL Connector, content.cfg gets overwritten with a new version. The new version of content.cfg does not list the constituent databases in the content database.
2. When the CA DataMinder Content Database service next starts, it scans all the constituent databases in the content database. If a constituent database exists but has no entry in the content.cfg configuration file, the service creates an entry and marks the constituent database as Read Only.
3. While the CA DataMinder Content Database service is running, the CA DataMinder IDOL Connector updates content.cfg and flags the constituent databases as Read-Write.

   However, the Connector cannot force the service to reread content.cfg.

Solution:

The CA DataMinder Content Database service only reads the content.cfg configuration file when the service starts. Therefore you must follow these steps:

1. Restart the CA DataMinder Content Database service
2. Restart any indexing jobs that are currently running.

More information:

TIMESLICE—Configure Batch Time Period