"Database Not Responding" Message Appears in Global Scan

This knowledge base article provides steps of one\napproach which may resolve a "Database Not Responding" (DNR) message\nin the Global Scan.

When a DNR message appears on the Global Scan page,\ncheck the uptime.log file for messages similar to the following line (numbers\nwill likely be different from example):

011-03-29 11:40:48,873 ERROR (ProtocolHandler:79) -\nIn command entities=168,169,171,175,176,177,179|commandType=query|commandQueryName=GET_GLOBAL_SCAN_ENTITIES

This type of message likely indicates that the\nGlobal Scan page is attempting to display recent performance data from an\nelement that has been removed or deleted from up.time.  To verify this condition, run the following\nqueries to see if there are entries in the entity_latest_data_sample table that\ndo not correspond to an existing element in the entity table:

select host_id from entity_latest_data_sample where\nhost_id not in (select entity_id from entity);

For each ID that is listed from the above query,\nrun the following two queries (replace <ID> with the ID number).  The first query should return an empty set\nbut the second should have one or more results.

select entity_id from entity where entity_id =\n<ID>;
select * from entity_latest_data_sample where host_id = <ID>;

To remove the erroneous performance data that is\ncausing this issue, run the following delete statement.

delete from entity_latest_data_sample where host_id\n= <ID>;

Once the delete statement has been run for each of the ID's from the first query, view the GlobalScan page\nto verify that the issue has been resolved.