Just Published! Threat Report: Exposing Malware in Linux-Based Multi-Cloud Environments | Download Now

Cb Protection: Frequent "Database timeout expired" generating Assets>Computers reports

Cb Protection: Frequent "Database timeout expired" generating Assets>Computers reports

Environment

  • Cb Protection 8.0.0.2562 (Patch 6) and earlier

Symptoms

  • When generating lists of computer reports, the Console can be either very slow or errors out with "Database timeout expired".
  • An error similar to this may show up in \Program Files (x86)\Bit9\Parity Server\Support\PHPErrors-date-here.log
    • Query: "WITH _inner AS (SELECT ROW_NUMBER() OVER( ORDER BY Upgrade_Status ASC ) AS RowNum, * FROM dbo.DetailedHostsGUI WHERE ( Deleted = 0 ) AND ( Host_Agent_Version = N'8.0.0.2562' ) ) SELECT * FROM _inner WHERE RowNum BETWEEN 1 AND 181 " caused error: DB Error: Could not continue scan with NOLOCK due to data movement.

Cause

This problem is triggered by including any of these columns in the Computer report:
Processor_Count, Machine_Model, Processor_Speed, Processor_Model, Memory_Size

Resolution

Code change EP-5109 is currently pending (March, 2018). The workaround is to avoid selecting any of the five columns

that trigger the very expensive join between two views.

Additional Notes

Check Patch Release Notes to see if EP-5109 is fixed.

Labels (1)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎03-14-2018
Views:
782
Contributors