Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Ensure Orion database tables have correct EngineIDs and WebsiteIDs so NPM can operate properly

Ensure Orion database tables have correct EngineIDs and WebsiteIDs so NPM can operate properly

Table of contents

Overview

For NPM to work properly, ensure Orion database EngineIDs and WebsiteIDs are correct for the following tables:

  • Alerts
  • EngineProperties
  • Events
  • NodesData
  • ReportJobs
  • ReportJobURLs
  • Syslog
  • Traps

Steps

  1. Open the Orion Database Manager
  2. Click Add Default Server
  3. Expand and select the Orion database
  4. To get EngineIDs, query the AllEngines table (in NPM 11.5.x) or the Engines table.
  5. To get WesiteIDs, query the Websites table.
  6. Query each of the following tables to check if the EngineID or WebsiteID values match with those from the AllEngines table and Websites table:
    • Alerts
    • EngineProperties
    • Events
    • NodesData
    • ReportJobs
    • ReportJobURLs
    • Syslog
    • Traps

 

If you have migrated check the tables below and other steps:

Check the following Tables for Old Server Name:

  • OrionServers, websettings, website, engine, subscriptions

In all tables:

  • OrionServers, websettings, website, engine, in Orion DB manager remove old engine value
  • Run the following query:

delete from pendingnotifications

delete from subscriptiontags

delete from subscriptions

Restart the Information Service V3 on all pollers (including the AWS).

 

 

 

Last modified

Tags

Classifications

Public