Network Management

Transaction log for SolarWinds Platform database is full

This article provides brief information and steps to resolve the issue when the SQL database is corrupted and the transaction log is full. Error: The transaction log for database 'SolarWinds_Orion' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases. SolarWinds Platform products. NPM.

First published date

10/30/2018 2:30 PM

Last published date

3/31/2026 4:54 PM

Overview

This article provides brief information and steps to resolve the issue when the SQL Server stops processing new transactions (i.e. save data, modify data) due to the transaction log being full. In logs, you can find a similar message:

Error Detail-System.Data.SqlClient.SqlException (0x80131904): The transaction log for database 'SolarWinds_Orion' is full. 
To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases


image.png

Product section

Orion Platform

Cause

The issue might be caused by any or all of below:

  • Insufficient disk space
  • Transaction log (LDF) autogrowth restriction
  • Unusually large or not being processed sufficiently transaction log

Resolution

  1. Stop all SolarWinds Platform Services on all polling engines and web servers.
  2. Back up the database. This will mark the data in the transaction logs as committed.  
  3. Shrink the log file to reclaim the space. For more information, see How to: Shrink a File (SQL Server Management Studio) 

NOTE: Steps specified are only applicable to databases using 'Simple' as its Recovery Model. For the Full Recovery Model, shrinking the Transaction Log requires taking a Full backup of the DB. Have DBAs perform the full backup instead
 

If the log and data files reside on the same drive, consider reviewing the following resource to help avoid future issues: