idash events recovering more than 30 hours

Products

• iDash Workload Automation for CA 7

Issue/Introduction

We can see that CA7IDASH has been recovering events for over 30 + hours. How can we stop these events from recovering and consuming a lot of CPU?

Environment

Release : 12.0

Component : CA WORKLOAD AUTOMATION iDASH FOR CA 7

Resolution

To resolve this issue the CA 7 instance was deleted from idash and it was re-defined to prevent recovery and this of course stopped ENF from consuming a lot of CPU