1 of 1 people found this helpful
I had the same issue and I have received the following answer from BMC Support:
I would like to inform you that the reason for this error to happen is corrupted event cache. The Event and Statistics cache can get corrupted at time due to various incidents such as an abrupt shut down of the PATROL Agent. You can fix the corrupted cache in two ways:
1] You can set up the variable given below setup the fix the corrupted cache at the time of agent restart.
Set the /AgentSetup/integration/GDD/enableEventFixCache and /AgentSetup/integration/GDD/enableStatFixCache configuration variables to "yes" to automatically run recovery when the agent restarts.
Note: This method should not be used as default. Fixing the cache is a resource intensive process and if automatic cache fixing is set by default, during the PATROL Agent start-up there might be cyclic abnormalities.
2] [Recommended] Run fix_cache command-line utility.
More information on fix_cache is available at fix_cache utility - Documentation for BMC PATROL Agent 11.3 - BMC Documentation