Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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_ret on Jul 06, 2016

Views: 1,570 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

Tags

Classifications

Public