What Would Cause The Triggering Of Impurge Esindex Events?
(Doc ID 2753673.1)
Last updated on FEBRUARY 22, 2021
Applies to:Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.
An imcheck -W was run and the expectation was to see a flurry of esindex tasks based on the usage.
The next morning, it was noticed that nearly 20,000 esindex tasks were in the maintenance queue.
There definitely was not nearly that number of folders accessed over night. The transaction log was checked and there were only a couple of hundred users logged in.
The default log showed impurge started processing esindex tasks at about 02:00 AM.
The only thing observed in the imsched tasks for that time would be a cron job for imdbverify.
What would have triggered the impurge esindex events?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!