Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > High blocking on the Orion database

High blocking on the Orion database

Updated November 22, 2017

Overview

High volume of blocking caused by the following procedure:

apm_dbm_APM_HardwareItemStatistics_DeleteOrphans

This procedure runs the following code:

DELETE TOP (@ChunkSize) orph FROM APM_HardwareItem_Detail orph LEFT JOIN HWH_HardwareItem parent ON orph.HardwareItemID = parent.ID WHERE parent.ID IS NULL

Environment

  • NPM 12.1
  • SAM 6.3 HF2

Cause 

Bug in SAM 6.3 and Hardware Health (HWH) 7.x caused by residual code before HWH was moved from SAM to a separate package. This residual code conflicts with HWH updates implemented in version 8.0.

The following database procedures should be deleted when upgrading from HWH 7.1 to HWH 8.0:

  • apm_dbm_APM_HardwareHierarchy_DeleteOrphans
  • apm_dbm_APM_HardwareItem_DeleteOrphans
  • apm_dbm_APM_HardwareCategoryStatus_DeleteOrphans
  • apm_dbm_APM_HardwareInfo_DeleteOrphans

Resolution

Update SAM to version 6.4 and install the latest hotfixes. 

 

 

Last modified

Tags

Classifications

Public