EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB422447: "The transaction log for database 'db_name' is full" error message occurs when attempting to upgrade MicroStrategy metadata residing on Microsoft SQL Server.


Community Admin

• Strategy


Article outlines why the error 'The transaction log for database 'db_name' is full.' occurs when attempting to upgrade a MicroStrategy metadata residing on Microsoft SQL Server.

SYMPTOM:
Users receive the following error when attempting to upgrade a Strategy metadata residing on Microsoft SQL Server through the Strategy Configuration Wizard.
 
Sample Code/Error
Error type: Odbc error. Odbc operation attempted: SQLExecDirect. The transaction log for database 'db_name' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases Could not create constraint. See previous errors. The statement has been terminated.
 It is seen that the error occurs on the following SQL statement:
Sql
BEGIN TRANSACTION
DECLARE @PKNAME_DSSMDOBJDEFN VARCHAR(255);
DECLARE @SQL_DSSMDOBJDEFN VARCHAR(255);
SET @PKNAME_DSSMDOBJDEFN = (SELECT name FROM sysobjects WHERE parent_obj=object_id('DSSMDOBJDEFN') and xtype='PK');
SET @SQL_DSSMDOBJDEFN = 'ALTER TABLE DSSMDOBJDEFN DROP CONSTRAINT ' + @PKNAME_DSSMDOBJDEFN;
EXEC (@SQL_DSSMDOBJDEFN);
ALTER TABLE DSSMDOBJDEFN ADD PRIMARY KEY (PROJECT_ID, OBJECT_ID, DEFINITION_SEQ);
COMMIT TRANSACTION
 
CAUSE:
One possible cause of the issue is the autogrow increment size for the metadata database file is set to too large. During the upgrade, the size of the database file will grow and when it is trying to allocate too much space for the file, the database run out of free space.
 
ACTION:
Contact your DBA to adjust the autogrow parameters for the metadata database files. Further details on the autogrowth setting in SQL Server is documented in the following link
 
http://support.microsoft.com/kb/315512
  
KB422447


Comment

0 comments

Details

Knowledge Article

Published:

May 25, 2017

Last Updated:

December 31, 2018