ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

EM logs filled with this error: ?[ERROR] [Lucene Merge Thread #0] [Manager] Uncaught Exception in Enterprise Manager:?

book

Article ID: 29182

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE

Issue/Introduction

 

Description:

The message below in the logs indicates a corrupt traces index/file:

[ERROR] [Lucene Merge Thread #0] [Manager] Uncaught Exception in Enterprise Manager:  In thread Lucene Merge Thread #0 and the message is org.apache.lucene.index.MergePolicy$MergeException: org.apache.lucene.index.CorruptIndexException: doc counts differ for segment _0: fieldsReader shows 1000 but segmentInfo shows 3

 

Solution:

Stop the EM and try any of these options.

 

Option 1: Run IndexRebuilder

Go to the tools directory of the Enterprise Manager, /opt/wily/prod/EM/Introscope9.1.0.1/tools and run IndexRebuilder.sh

 

The script requires specifying the traces directory such as shown in the following example:

./IndexRebuilder.sh ../traces

 

Option 2: Create new traces directory

If the first option did not work, stop the Enterprise Manager, rename the traces directory (/opt/wily/prod/EM/Introscope9.1.0.1/traces) to traces_old and restart the Enterprise Manager. This will automatically recreate a new traces directory.

 

Note: EM has to be stopped while performing any of the above activity.

Environment

Release:
Component: APMISP