I constantly get this message but am unable to run database maintenance till completion. It always hangs when removing older data from traps.
Any ideas?
I had an issue recently where maintenance was failing due to the log drive on the SQL server filling up. How full are the drives on your SQL server, especially the drive with your log files?
This can also occur when the volume where the TempDB is stored does not have enough space. It can be tricky to catch since it can grow by several gigabytes only when maintenance runs. So it can look fine normally.but when database maintenance runs it consumes all the space on the drive then database maintenance fails and it shrinks back to normal size.
Here's a screenshot of the disks.
If you are running SAM 6.1 or later the issue may be related to an issue identified in an earlier version of SAM that is outlined in the KB below, including the resolution.
I think this will resolve the SAM maintenance issue but if database maintenance won't finish because it is stuck at "Removing older data from Traps" it won't help.
Can you kick off a maintenance, and then let me know how much space is left on your log drive once it fails?
I've had a similar issue in the past with 'SAM Database Maintenance Is Overdue'. I opened a support case (Case #619240) and the following fix was provided. I hasten to add you might want to refer to Solarwinds Support before attempting this as your issue could be different.
Are you running the latest version of SAM?
** Before doing any work on your database please make sure that you have a current backup as this will make a permanent change to your database. **
1. Start > SolarWinds Orion > Advanced Features > Database Manager
2. Click on Add default server, then right-click on the SolarWindsOrion database and select New query
3. Paste and execute the following query:
UPDATE APM_ProcessEvidence_Detail SET PercentCPU = NULL WHERE PercentCPU < 0
4. Run the Database Maintenance manually (Start > SolarWinds Orion > Advanced Features).
I will try the truncate option, I'm not worried if the traps go away. I would think you'd need to stop the traps service before running the truncate as you don't want it dumping data into it while truncating.