Transaction log for [database] is full

3 Years Ago
JorgeR
MANAGEMENT CONSOLE

Summary

Bizagi's database registers all events performed to have several restoration points to perform system recovery.
When the server’s hard disc is running out of space some system operations may be affected and an the error "Transaction log for [database] is full" is displayed in the web server’s logs.

Applies to

Bizagi 10.x with SQL Server Database Server

Symptoms

Bizagi cannot perform any system operation and the web server’s logs displays occurrences of the following message:

The transaction log for <database> is full

Cause

The error message is presented because there is no available space in the log viewer of the database server, therefore, no system operation that updates data can be performed. In addition to the above, this error can also be presented because the database was configured with Full Recovery Model and the the transaction log has not been periodically backup to free space in such log.

Solution

DEVELOPMENT AND TESTING ENVIRONMENTS
In development and testing environments, it is recommended to configure the database with Simple Recovery Model. In such mode, the transaction log is periodically cleaned automatically.
Refer to
https://msdn.microsoft.com/en-us/library/ms189272.aspx

To get back the space used by the transaction log refer to the following article
https://technet.microsoft.com/en-us/library/ms178037(v=sql.105).aspx

If the Simple Recovery Model is active for your database and the mentioned error is presented, it is more likely that the current log space for the generated transactions is not enough, so you have to increase the space size. If autogrow is enabled, the disc size may not be enough.

For further information, please refer to https://msdn.microsoft.com/en-us/library/ms175495(v=sql.110).aspx

PRODUCTION ENVIRONMENT
In Production environments, it is recommended to configure the database with Full Recovery Model that guarantees a better system recovery in case of a failure. This mode requires to periodically take a backup of transaction log in order to clean up the space and keep the information recorded in the log.

If the Full Recovery Model is active for your database and the mentioned error is presented, it is more likely that the current log space for the generated transactions is not enough, so you have to increase the space size. If autogrow is enabled, the disc size may not be enough.

For further information, please refer to https://msdn.microsoft.com/en-us/library/ms175495(v=sql.110).aspx


Details

Last Modified:3 Years Ago
Last Modified By: Andread
Type: ERROR
Level: Expert
Article not rated yet.
Article has been viewed 6.0K times.

Options