Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > The attempted insert or update of the partitioned view failed because the value of the partitioning column does not belong to any of the partitions

The attempted insert or update of the partitioned view failed because the value of the partitioning column does not belong to any of the partitions

Created by Adrian Cook, last modified by Rodim Suarez on Jul 06, 2016

Views: 108 Votes: 1 Revisions: 5

Updated

Overview

If the you are getting a notification for database maintenance that it is overdue, check the C:\ProgramData\SolarWinds\Orion\SWDebugmaintenance.log to see if the below or similar error is present:

ERROR SolarWinds.Data.DatabaseMaintenance.StandardTableHandlerDAL - Failed to execute procedure: dbm_CiscoBuffers_DetailToHourly
System.Data.SqlClient.SqlException (0x80131904): The attempted insert or update of the partitioned view failed because the value of the partitioning column does not belong to any of the partitions.

Environment

NPM 11.5 and later

Cause 

The view that the maintenance is trying to roll the data up to does not exist. It is mostly caused when the maximum value for retention has exceeded on one or more of the settings. For example, detailed data kept for 90 days and the maximum value is only 60 days.

Resolution

  1. Go to Settings > Polling Settings and reduce the retention to a value below the maximum and then click Submit.
  2. Let the database maintenance run and once it completes the notification should go away.

 

Last modified
17:50, 6 Jul 2016

Tags

Classifications

Public