You should check the documentation that comes with ADDM. See these links for starters:
This will give you a very good understanding of log files that are used in ADDM. Also how to increase the logging level etc. Also create an account for yourself on docs.bmc.com if you havent done that already. A few links there which will be of your interest:
Please use the latest (ADDM 8.3) version of the documentation.
There is also some sections about troubleshooting and many other topics you can search using the left-hand side "Space Search" area (just type in few keywords and you will get some instant suggestions).
Finally it is recommended for a beginner (but not only) to go through the Community Enablement Tutorials.
Go and have a look to Stalled discovery runs (this is the first proposed link if you type "hold" on the "Search Space" right-hand field).
The simplest case is that you started some scheduled runs but the scan window is too small to finish discovering all the target IPs. See Controlling discovery for an explanation of the "Duration" parameter of scheduled scan run as well as Configuring Discovery scanning setting for a explanation of the "Minimum time before end of window to avoid starting new scheduled discovery operations" parameter.
Thank you for the suggestion.
But my question here is those schedule runs were success in the last one month and only on hold in the last couple of dates. So is this some kind of performance Issue.. if so what are the steps to debug that..
And I havnt change any schedules runs till now...
So you confirm that the scheduled runs are on hold because they are not able to finish their job within the scan window, although they were able to do so some time ago.
Which ADDM version do you use? What kind of slow down have you observed on your scheduled discovery runs duration (please provide some examples)? Did you also observed other performance degragation?
Please have a look to the blog post "Does reasoning slow down?". It describes one of the main issue addressed by ADDM 8.3 SP2. It might address yours.
Thank you Brice for swift response.
We are using 8.2 ADDM.
What are the steps to check that all you mentioned above? What exactly do we need to look into log?
Does ADDM maintain any type of cahce that we need to clear on regular basis ? If so does it have any Impact on currently onHold scans?
It is OK to restart the Appliance. It might help performance of your discoveries since you are using ADDM 8.2.
To speed up your discoveries, since you noticed a slowdown, you can increase your DB Cache size, up to 1/2 the size of RAM available on your appliance.
To change your DB Cache size:
Click Administration -> Model Maintenance -> Cache Size
The default is 1GB. If your RAM size is 8G, then maybe try setting your DB Cache Size to 3gig or 4gig.
You must restart your appliance after setting the Cache Size for the appliance to use the new value.
The default DB Cache size was increased to 1/2 the size of RAM in ADDM 8.3.2: