Loading...

Knowledge Center


Stale records appear on the Inventory page when a Purge System Inventory task is run immediately after a client has been removed from ePolicy Orchestrator
Technical Articles ID:   KB88248
Last Modified:  12/15/2016
Rated:


Environment

McAfee Application and  Change Control (MACC) 8.x, 7.x, 6.2.x, 6.1.x
ePolicy Orchestrator (ePO) 5.x
 

Summary

This article explains what happens when a Purge System Inventory task is run immediately after a client has been removed from ePolicy Orchestrator, the potential issues that may arise from running the task, and the process for correcting these issues.

Problem

Running a Purge System Inventory task before the internal Inventory Clean Up Task has had a chance to run results in the client inventory entering an orphaned state.

Cause

The following actions occur when the Purge System Inventory task is run:
  • Identification of AGENTGUIDs from SCOR_INV_SYSTEM_PROPERTIES table whose INVENTORY_FETCH_TIME is older than one (1) day.
  • Deletion of all records from SCOR_HOST_BINARY_ASSOC for those AGENTGUIDs.
  • Deletion of the AGENTGUID from SCOR_INV_PROPERTIES.

NOTE: Records are not deleted from SCOR_INV_BINARIES, SCOR_INV_APPS or SCOR_BINARY_PATHS.
 
If the Purge System Inventory task runs before the internal Inventory Clean Up task has had a chance to run, stale records will appear on the Inventory page. When the stale records appear, the internal Inventory Clean Up task is unable to remove the records. This is because:
  • The AGENTGUIDs that are in SCOR_INV_SYSTEM_PROPERTIES are not found in the EPOLeafNode. Because the AGENTGUIDs are not present in the EPOLeafNode, the Purge System Inventory task deletes the AGENTGUIDs from SCOR_INV_SYSTEM_PROPERTIES.
  • With the AGENTGUIDs deleted, the internal Inventory Clean Up task cannot complete because it performs the clean-up based off the AGENTGUID.
NOTE: The internal Inventory Clean Up task runs every 72 hours by default.

Solution

To remove the orphaned inventory entries, run the following queries against the ePO database:
 
delete from SCOR_INV_BINARIES where BINARY_ID not in (select DISTINCT
BINARY_ID from SCOR_HOST_BINARY_ASSOC)
 
delete from SCOR_INV_APPS where APP_ID not in (select DISTINCT APP_ID from
SCOR_INV_BINARIES)
 
delete from SCOR_BINARY_PATHS where ID not in (select DISTINCT
BINARY_PATH_ID from SCOR_HOST_BINARY_ASSOC)

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Languages:

This article is available in the following languages:

English United States
Japanese

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.