Support Article
Re-index ends with "Transitioning from [RUNNING] to [FAILED]."
SA-41006
Summary
Users experience empty result set when performing searches in Pega environment.
Attempting to re-index finishes in an error state. "Work index file unavailable or corrupted"
Error Messages
2017-07-06 04:16:35,564 [ PegaRULES-Batch-3] [ STANDARD] [ ] [your_ruleset:01.01.01] (pboard.DirectStreamContainerV7) ERROR your_operator - Problem reading java object from stream for pySummaryCount; substituting dictionary attribute '@Z:u?N:' for invalid stream attribute '@Z:u?N:'
Setting logger for class AbstractIndexer to debug reveals this after the above error.
2017-07-06 07:19:14,035 [ PegaRULES-Batch-4] [ STANDARD] [ ] [your_ruleset:01.01.01] ( internal.es.AbstractIndexer) DEBUG namratam - Transitioning from [RUNNING] to [FAILED].
Steps to Reproduce
Not Applicable
Root Cause
A defect in Pegasystems’ code or rules
There are several work objects that appear to be corrupted.
The indexes are built, but are incomplete due to the missing work objects that could not be read properly.
Resolution
The indexing appears to 'fail', but in reality it is intact and can be used successfully.
Published August 26, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.