Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

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

Database maintenance is overdue issues

Created by Alexander Aguilar, last modified by Alexis Pasao on Sep 21, 2018

Views: 4,945 Votes: 5 Revisions: 17

Updated: September 21, 2018

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.

 

Reason for Rework or Feedback from Technical Content Review:

 

 

Last modified

Tags

Classifications

Public