This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Database Maintenance Hanging on "Summarizing detailed data from InterfaceAvailability" Step

bharris1 over 7 years ago

This morning I had a "Database Maintenance is Overdue" alert when I logged in. About 4 hours ago, I logged into my main poller and kicked off a manual Database Maintenance. Now, 4 hours later it is still sitting on "Summarizing detailed data from InterfaceAvailability." I looked in swdebugmaintenance.log and there are no errors after "Summarizing detailed data from InterfaceAvailability." Any thoughts or suggestions?

0 neomatrix1217 over 7 years ago

This is a known issue can you open up a support ticket.
Cancel
Vote Up 0 Vote Down

Cancel
0 bharris1 over 7 years ago in reply to neomatrix1217

I'll do that. Thanks
Cancel
Vote Up 0 Vote Down

Cancel
0 bharris1 over 7 years ago in reply to neomatrix1217

neomatrix1217 Do you know what the problem is? Just curious. I have opened a ticket but they haven't started it yet.
Cancel
Vote Up 0 Vote Down

Cancel
0 neomatrix1217 over 7 years ago in reply to bharris1

What is your case #?
Cancel
Vote Up 0 Vote Down

Cancel
0 shivani.aggarwal over 6 years ago

Hi bharris, Was your issue resolved?
I am having the same issue and wanted to know if there is a resolution before opening a support case.
Cancel
Vote Up 0 Vote Down

Cancel
0 bharris1 over 6 years ago in reply to shivani.aggarwal

I ended up restarting the server and manually rerunning the maintenance and it completed fine. It just takes a VERY long time if you are monitoring a lot of interfaces.
Cancel
Vote Up 0 Vote Down

Cancel
0 sum_giais over 6 years ago in reply to bharris1

I had this happen once and turns out the SolarWinds log *.ldf file from the database was in need of more space. The volume in which the database held that file was out of space because the file grew so drastically. This was an extreme scenario though where massive edits etc. had happened prior. Certainly would want to hear back from support before doing anything but that could at least be a quick check..
Cancel
Vote Up 0 Vote Down

Cancel
0 wlouisharris over 6 years ago

We have had a similar problem. We run into the issue every few months and I'm not sure what triggers the condition. Typically we will either truncate the largest table or the issue will subside after a few consecutive intervals where maintenance does run. The suggestion from support is lower retention or truncate tables. We can't lower settings due to strict customer requirements. The other suggestion is a physical SQL server and or flash storage which is no short putt.
Cancel
Vote Up 0 Vote Down

Cancel