Skip to main content

Error: 'The transaction log for database is full due to active transaction'

What to do if you see a full transaction log error in Orchestrate when viewing the demand planner or running a data import.

Written by Arthur Ashdown

You may see this error when viewing the demand planner in a plan:

⚠️Error: An unexpected error occurred. Please report this problem to your system administrator with the following information: System.Data.SqlClient.SqlException: the transaction log for database 'DATABASENAME' is full due to ACTIVE_TRANSACTION.

Or, you may see this error when running a data import:

⚠️Error: Orchestrate Data Flow import has failed. The detailed information is as follows:
the transaction log for database 'DATABASENAME' is full due to ACTIVE_TRANSACTION
Import command:
​EXEC [wf].[pr_Merge_orc_orders]


In both cases, the database transaction logs need shrinking. Please raise a new case online and reference the title of this article. A member of our Support team will be happy to help.

Did this answer your question?