At times, when the record extractor is run in batch or update mode, it might fail to process records. When this occurs, the record extractor creates repair files corresponding to the failed records. The repair files are written to the directory where the ClearQuest search properties file, CQ-db_name-dbset_name.xml resides, which is typically the Solr home directory. Monitor this directory to check for instances of failed processing and use the record extractor in repair mode to process the problematic records. See the cqtsdbcrawler reference help for usage information.
By default, no operation log (oplog) purging occurs in the user database. When you implement an oplog scrubbing policy to minimize wasted space, use caution to avoid removing oplogs prematurely. Oplogs should exist long enough for the update-mode record extractor to process. If the update-mode record extractor does not run for a long period of time, when it resumes, it starts by processing the oldest update oplogs that have not been processed.
If you are running ClearQuest MultiSite, your full-text search oplog scrubbing policy should not be more aggressive than the existing ClearQuest MultiSite oplog scrubbing policy.
See the ClearQuest Multisite help on oplog scrubbing for details.
Over time, as new ClearQuest records are added, modified, and deleted, the Lucene index becomes fragmented, which can degrade performance.
cqperl cqtsdbcrawler.pl -optimize CQ-db_name-dbset_name.xml -site site_name
If you are not running ClearQuest MultiSite, you can omit the -site option. See the cqtsdbcrawler reference help for usage information.
The Solr search engine should not impede ClearQuest performance. However, if you suspect it does, first try optimizing the Lucene index, as discussed in the previous section. Also consider the following measures to optimize Solr performance:
Note that you may need to temporarily increase the JVM memory allocation when you run the record extractor in batch mode and then reset it.
The update-mode record extractor will use the updated ClearQuest search properties file the next time it indexes.
cd %SOLR_HOME%\yourSchemaName\Solr\exampledocs\
java -Ddata=args -jar post.jar "<delete><query>record_type:recordTypeName</query></delete>"
cd $SOLR_HOME/yourSchemaName/Solr/exampledocs/
java -Ddata=args -jar post.jar "<delete><query>record_type:record_type</query></delete>"