Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Network Performance Monitor (NPM) > Database maintenance is overdue issues

Database maintenance is overdue issues

Created by Alexander Aguilar, last modified by Aileen de Lara_ret on Oct 04, 2016

Views: 894 Votes: 3 Revisions: 16

Overview

This article provides brief information and a resolution to the issue when the Database maintenance become overdue.

Environment

NPM version 11.x

Cause 

Cause 1:

Traps messages set to high at 8000000 days.

Look at the swdebugMaintenance.log

Log location: C:\ProgramData\Solarwinds\Logs\Orion

 

Cause 2:

Further down in the swdebugMaintenance.log you might see a very high number of Trap rows and Trapvarbinds rows. For example in this scenario we saw that there were 350+ million rows for Trapvarbinds when the warning threshold was set for 5,000,000 and then there were also 40+ million rows for Traps when the warning was set for 1,000,000.

Note: Syslog table also has a maximum threshold of 1,000,000 rows only.

Resolution

​Resolution for Cause 1:

  1. Set Trap Messages Retention to 90 days - Default database retention settings.
  2. Run database maintenance manually.

 

Resolution for Cause 2:

  1. Open the Database Manager and load the default database.
  2. Right click the database instance and select "New Query".
  3. Input the following query:
    truncate table traps
    truncate table trapvarbinds
  4. Click Execute.
  5. Now, either run the database maintenance manually by running the Database Maintenance from the SolarWinds folder or wait for the default maintenance window which 2:15 AM nightly by default.

 

 

Last modified

Tags

Classifications

Public