Database Maint Failure - VIM_dbm_VirtualMachines_ComputeStorageDepletion - Arithmetic overflow error

Burner087

Not a SQL guy. Looking to figure out how to find the nodes that are causing this issue and fix it. Thanks.

2026-07-15 07:25:14,789 [4] ERROR SolarWinds.Data.DatabaseMaintenance.StandardTableHandlerDAL - Failed to execute procedure: VIM_dbm_VirtualMachines_ComputeStorageDepletion
System.Data.SqlClient.SqlException (0x80131904): Arithmetic overflow error converting expression to data type bigint.
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at SolarWinds.Data.DatabaseMaintenance.StandardTableHandlerDAL.InternalExecuteStoredProc(String procedureName, SqlParameter[] parameters, CommandType commandType)
ClientConnectionId:f938e7b6-aeaa-4118-9182-1702e23f9af6
Error Number:8115,State:2,Class:16
2026-07-15 07:25:14,804 [4] INFO SolarWinds.Data.DatabaseMaintenance.MaintenanceEngineHelper - Failed to execute 'Compute forecast coefficients [VIM_VirtualMachines]'
System.Data.SqlClient.SqlException (0x80131904): Arithmetic overflow error converting expression to data type bigint.
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteScalar()
at SolarWinds.Data.DatabaseMaintenance.StandardTableHandlerDAL.InternalExecuteStoredProc(String procedureName, SqlParameter[] parameters, CommandType commandType)
at SolarWinds.Data.DatabaseMaintenance.StandardTableHandlerDAL.Execute(String procedureName, DateTime date)
at SolarWinds.Data.DatabaseMaintenance.StandardTableHandler.ComputeForecastCoefficients(DateTime asOfDate)
at SolarWinds.Data.DatabaseMaintenance.MaintenanceEngineHelper.ExecuteMaintenanceAction(Action maintenanceAction, OperationSeverity severity, String actionName, String actionTarget)
ClientConnectionId:f938e7b6-aeaa-4118-9182-1702e23f9af6
Error Number:8115,State:2,Class:16

mr.castaneda

This one is usually a VIM DB maintenance issue rather than a generic SQL problem. In the cases we’ve seen, the failure happens in VIM_dbm_VirtualMachines_ComputeStorageDepletion while it is calculating VM storage depletion forecasts, and it can be triggered either by very large VIM datasets or by an older version of the stored procedure that does not include the overflow guard.

The good news is that this usually does not impact core monitoring or alerting. The main thing it tends to affect is the VIM capacity forecasting side of DB maintenance.

If you want to check which VM rows are likely causing it, run this in SSMS against the SolarWinds database:

SELECT TOP 200    vms.VirtualMachineID,    vms.DateTime,    vms.AvgVolumeSummaryCapacity,    vms.AvgVolumeSummaryFreeSpace,    CAST(vms.AvgVolumeSummaryCapacity AS decimal(38,0)) -    CAST(vms.AvgVolumeSummaryFreeSpace AS decimal(38,0)) AS UsedSpaceDecimalFROM dbo.VIM_VMStatistics vmsJOIN dbo.VIM_VirtualMachines vm    ON vm.VirtualMachineID = vms.VirtualMachineIDJOIN dbo.VIM_Hosts h    ON h.HostID = vm.HostIDWHERE h.PlatformID = 1  AND vms.AvgVolumeSummaryCapacity > 0  AND (      CAST(vms.AvgVolumeSummaryCapacity AS decimal(38,0)) -      CAST(vms.AvgVolumeSummaryFreeSpace AS decimal(38,0))  ) > 9223372036854775807;

If that returns rows, those are the VM records I’d focus on first.

If it comes back blank, that does not completely rule the issue out. We’ve also seen cases where the real problem was that the environment still had an older copy of dbo.VIM_dbm_VirtualMachines_ComputeStorageDepletion, even on a newer platform version. In that situation, the next things I’d collect are:

• The current stored procedure definition for dbo.VIM_dbm_VirtualMachines_ComputeStorageDepletion.
• Table size output for these three tables:

EXEC sp_spaceused 'VIM_VMStatistics';EXEC sp_spaceused 'VIM_VirtualMachines';EXEC sp_spaceused 'VIM_Hosts';

• A fresh set of diagnostics right after a failed DB maintenance run.

If you’re asking whether this is something you can usually “fix” just by cleaning up a node, I’d say not always. In a lot of the cases we’ve seen, Support/Engineering needed to validate the data and then provide or confirm the corrected stored procedure for that environment.

So short version: run the query above first, see if it points to specific VM rows, and if not, grab the procedure definition plus the sp_spaceused output and open a support case with that attached.

We hope this information is useful.