ERROR [HOST-INSTANCE-lowPriorityPool-2-[DBSS_File_Group][]] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - Failed to run DBSSFileGroupProcessor processor of DBSS_File_Group collection.
java.lang.RuntimeException: Failed to execute collection [DBSS_File_Group], reason=[Foglight][SQLServer JDBC Driver][SQLServer]Could not allocate a new page for database 'tempdb' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup
ERROR [HOST-INSTANCE-lowPriorityPool-1-[DBSS_Logical_Disks][]] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - Failed to run DBSSFileProcessor processor of DBSS_Logical_Disks collection.
java.lang.RuntimeException: Failed to execute collection [DBSS_Logical_Disks], reason=[Foglight][SQLServer JDBC Driver][SQLServer]Could not allocate a new page for database 'tempdb' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.-
If a collection is failing – the data is not collected and hence any alarm that relies on it will not be triggered. When any collection fails there should be an alarm.
For the DBSS – File Group Utilization and DBSS - Log File Utilization alarms
Specifically for the message ‘Could not allocate a new page for database 'tempdb' - there is a specific alarm for named: "DBSS - TempDB Out of Storage"
Usually, not all of the space is exhausted between two executions of the collection – so that when the used space exceeds the alarm thresholds and begins to get low – users will get an alarm.
In a normal situation, the customer may receive
DBSS - File Group Utilization or DBSS - Log File Utilization alarms
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center