Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

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: 1,074 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