Error : A database error occurred : The transaction log for database 'K2' is full.

  • 29 October 2012
  • 2 replies
  • 19 views
G
Badge +5

Hi,


I am getting below error when i try to deploy process through K2 Designer For Visual Studio.


Error 1 A database error occurred : The transaction log for database 'K2' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases.


In Application Event Viewer i found below error:


K2LogServer::ServerThread: 24129 A database error occurred : The transaction log for database 'K2' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases


Did anyone get this error?


Please suggest me the steps to resolve this error....


Regards,


Reddy

2 replies

B
Badge +11

You can shrink the transaction log file if you change the recovery mode from full to simple, using following commands: 


ALTER

DATABASE
myDatabase
SET


RECOVERY SIMPLE


DBCC
SHRINKDATABASE
(
myDatabase
,

5
)



then you switch back to full recovery





ALTER

DATABASE
myDatabase
SET
RECOVERY
FULL





W
Badge +4

Hi gsreddy,


 


Space permitting, I would recommend that you just increase the size of your log file for now. The article shows how you can increase the file size using SQL Management Studio or a Transact SQL statement. For more information please see the following article: http://technet.microsoft.com/en-us/library/ms175890.aspx.

Alternatively, if you are running low on space, you can add another log file to the DB and point it to a different location. For more on this, please see: http://technet.microsoft.com/en-us/library/ms175890.aspx.

Simply setting the log file growth to unlimited, should get you past the problem. But, I would start thinking about performing some DB maintenance in the semi-near future. Here is a nice little article that explains a couple of backup stratagies: http://technet.microsoft.com/en-us/library/ms191239(v=sql.105).aspx

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings