This alarm is raised when a log is almost full and the log files cannot automatically grow enough to relieve the problem. When the free space in a database’s log file falls below a certain percentage of the log file’s current total log size, the alarm is raised. Once a log fills completely, all attempts to update anything in that database will fail. This alarm takes into account the amount of free space currently within a fixed sized log file.
This alarm can occur when a log is filling up and all files in the log are approaching, or have reached, their MaxSize settings, or are defined with Auto Grow=No.
When this alarm is current, you should first look at reducing the log requirements by:
- On the SQL Server | Databases drilldown | Databases grid, check the Transactions information to see if there is a very long running transaction for the database in question. To do this, from the View list select Transactions and then look at the Oldest Tran Start Time column.
- Backing up (or truncating) the log for the database in question. This removes any log entries that have been committed.
If you cannot identify or resolve the cause of the problem using the above tips, consider increasing the amount of space allocated to the logs by:
- View the SQL Server | Databases Drilldown | Transaction Logs page | Transactions Logs grid. The logs in danger are those that have a low Free Pct figure. Click the column heading to sort by this field. You can also identify the logs in danger by using the Transaction Log Growth chart, and looking for logs showing a high used percentage figure in the Transaction Logs grid.
- View the SQL Server | Databases Drilldown | Log Files page. This displays the files that were identified as being in danger. Check for files with Auto Grow=No or those that have their current size nearing their MaxSize. If necessary, adjust the file growth parameters.
To increase the amount of space a log can use:
Adjust the file growth parameters of at least one log file in this database so that it can grow. Make sure the Auto Grow setting is on, and that the MaxSize setting is larger than the current file size.
In Spotlight Enterprise from the Spotlight Client you can configure this alarm to ignore certain values. You can configure different alarm severities for specific log files.