This message indicates that historical data in SAM tables have not been summarized. Likely because database maintenance hasn't probably executed for several days, or the database maintenance is failing for some reason. Please try to run database manually following the instructions outlined below. If the error message persists please open a case with support so we could investigate Database Maintenance log file.

Run the database maintenance.

http://www.solarwinds.com/netperfmon/SolarWinds/OrionAPMAGRunningDatabaseMaintenance.htm

Note: Administrative privileges are required to run Database Maintenance.

To run the Database Maintenance utility from the Orion Web Console:

1. Click Settings in the top right of the web console, and then click Poller Settings in the Settings group.
2. Click Perform Maintenance Now in the Database Settings area.

To run database Maintenance from the Start menu:

• Click Start > All Programs > SolarWinds Orion > Advanced Features > Database Maintenance, and then click Start.

Hi running the Maintenance Plan manually from the Start menu cleared the alerts.

Question; Will the alerts simply come back in several days if I don't run the plan manually again? Has this task been scheduled before and how do I health check the state of said schedule?

Maintenance should occur nightly at 2:15am (by default). This can be configured under [Settings - Polling Settings - Database Settings - Archive Time]. If the Orion or SQL server are configured to reboot or perform some other maintenance routine at this time it may be preventing maintenance from occurring properly. It's also possible that some other issue was occurring during maintenance (errors/timeouts/etc) that has since been cleared by performing this maintenance manually. If you haven't yet upgraded to SAM 5.5 I recommend doing so, as there have been several improvements to the maintenance tasks in that release. If after upgrading the message still returns please open a case with support so we can troubleshoot this issue further.

Hi ">aLTeReGo,

What if the Database Maintenance appears to be hung at one point after 12 hours?

I've been shutting it down after awhile.

Are there other maintenance tools I should be using on the SQL database server itself?

THanks so much everyone,

Cheryl

Hi, I faced a similar issue - root cause was fragmentation on DB. Defragmentation needs to performed on DB to resolve the issue.

Follow the below link

http://knowledgebase.solarwinds.com/kb/questions/3202/Critical+index+fragmentation+detected+during+database+maintenance

Correct Vinay BY. Regular non-Orion specific database maintenance should be performed to keep the database and indexes up to date.

One of the challenges we face is that  - since we have a lot of applications where the vendor and/or developer has insisted on a hands-off approach from our DBA team, the policy is that nobody does anything with a database unless explicitly instructed to do so.

Where can we get a list of these "non-Orion specific database maintenance tasks" that we should be performing?

Regular activities of SQL DBA

Brad's Sure DBA Checklist

I think the point is that they are not "Non-Orion Specific DBA Tasks" that you should be applying to your SAM database, rather DBA Tasks that should be maintained for all databases, regardless of the application / vendor?

Hi, I am getting same error. I run database maintanence manually but nothing has changed.I haven't see any error when i run database maintanence manually.

Database maintenance occurs daily at 2:15 AM (configurable under [Settings - Polling Settings]. If there are other tasks occurring on either the Orion server or the SQL database server at this time such as nightly reboots, WindowsUpdates/Patching, backups, defrags, antivirus scans, etc. These can all influence the success or duration of database maintenance.