debugsqlMinor
Error 9002. The transaction log for database is full due to 'NOTHING'
Viewed 0 times
dueerrorthefulllogdatabasenothingtransactionfor9002
Problem
In the SQL Server Error Log (and Windows Event Viewer) I found the error message:
The transaction log for database [...] is full due to 'NOTHING'.
What does a reason of "NOTHING" mean?
If there is no reason which prevents the log from being reused, then why does this error message exist?
The transaction log for database [...] is full due to 'NOTHING'.
- The database is in SIMPLE recovery model.
- Its log has 126 VLFs.
- It is a user database, not a system one.
What does a reason of "NOTHING" mean?
If there is no reason which prevents the log from being reused, then why does this error message exist?
Solution
NOTHING is basically a 'Not any of the other reasons' status. Other Log Full status values I've seen are: LOG_BACKUP, REPLICATION, and CHECKPOINT.
As to the cause, check the log file max size & growth properties. Then compare them to the available disk free space. The log file may have reached the Max size, or the disk may not have enough free space to accommodate the next growth interval/amount.
As to the cause, check the log file max size & growth properties. Then compare them to the available disk free space. The log file may have reached the Max size, or the disk may not have enough free space to accommodate the next growth interval/amount.
Context
StackExchange Database Administrators Q#178016, answer score: 3
Revisions (0)
No revisions yet.