Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Network Performance Monitor (NPM) > Background upgrade for interfaces cannot complete

Background upgrade for interfaces cannot complete

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 35 Votes: 0 Revisions: 12

Issue

The "Background upgrade for a history table started" event is triggered repeatedly, but there is no appropriate event announcing that the upgrade has been completed. Some historical data seems to be missing. 

Environment

All NPM versions

Cause

Before the upgrade, your historical tables contained too old data, or data with a date in the future. Historical data thus cannot be migrated. The background upgrade, also called "lazy upgrade", cannot complete, and some historical data is therefore missing.

Resolution 

Run the attached script to resolve the issue.

Warning: SolarWinds strongly recommends that you only apply the script if you are experiencing the issue. Follow the instructions exactly and run the script. Failure to follow these instructions can introduce errors into the database or may create an error state.

To apply the script:

  1. Download the attached script.
  2. Run the Database Manager in theSolarWinds Orion > Advanced Features program folder.
  3. Connect to your database server and select your database. By default, the database name is SolarWinds Orion.
  4. Right-click the database name and select New Query.
  5. Copy and paste provided script.
  6. Run the script, for example by pressing the F5 key.

The script can take several minutes/hours to finish. It depends on the amount of data that needs to be processed in the database. When the script is finished, the lazy upgrade will complete, and all historical data will be available.

 

In the event however that the issue still occurs and the data is still populated in the tables the query impacts, you have 2 options on proceeding:

  1. Modify the query for larger table clear count.
    1. Edit the query
    2. Look for the line with Set @ChunkSize = 10000
    3. Increase the @ChunkSize = 10000 to something higher, possibly 20000 up to 100000
    4. Save query
    5. Run again
  2. Truncate the tables. It's possible that the query cannot clear all the data or the tables have corrupt data. In such a case, truncating the tables would be for the best 
    1. Log in directly to the SQL server
    2. Run the following queries:

Truncate table Migration_InterfaceTraffic_Detail

Truncate table Migration_InterfaceTraffic_Hourly

Truncate table Migration_InterfaceTraffic_Daily

Truncate table Migration_InterfaceErrors_Detail

Truncate table Migration_InterfaceErrors_Hourly

Truncate table Migration_InterfaceErrors_Daily

 

Last modified
21:47, 22 Jun 2016

Tags

Classifications

Public