search cancel

AWA: Lucene index not updated anymore after loading an object with modification date in the future

book

Article ID: 202383

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

The Lucene index maintained by the JCP in version 12.3.x  is not always updated correctly.

After having some end users importing objects with a modification date in the future ( via a transport case / XML or similar), the JCP starts using this wrong modified date as baseline to index new objects and since it's in the future the newly created objects are no longer indexed.

For example, if the object has not been added to the Lucene index, it is impossible to add the object to a workflow.

Search in AWI does not find newly created objects either.

Cause

A problem has been fixed, where the Lucene Indexcache was not kept up to date when an object with a modification that is set in the future was indexed.

Environment

Release : 12.3.x

Component : AUTOMATION ENGINE

Resolution

Workaround:

Rebuild the lucene index by renaming the subfolder indexCache after having stopped the JCP responsible for the Lucene Index.

This is explained here:

how to rebuild index search


Solution:

Update to a fix version listed below or a newer version if available.

Fix version:
Component(s): Automation.Engine


Automation.Engine 12.3.3HF5 - Available 
Automation.Engine 12.3.4HF1 - Available 
Automation.Engine 12.3.5 - Available

Additional Information

example of log line: U00045410 Search index update: The modification time of object (oh-idnr=102296, client=0, type=HOST, moddate=2021-08-05T10:50:14Z) is in the future. The current time will be used instead.