Multiple transactions are written to the t-log of the DB.

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
lduresky
Posts: 20
Joined: Thu Mar 30, 2006 10:18 am

Multiple transactions are written to the t-log of the DB.

Post by lduresky » Thu Jan 11, 2007 10:15 am

I tried to reply to the topic listed above (http://support.sourcegear.com/viewtopic ... ction+logs), but it was a Gold Support Forum and I don't have access to reply to it.

We're using Vault 3.1.8.3771 and we are also seeing problems with a full transaction log. After discovering it, we recently changed the database from Full to Simple recovery mode and increased the max log file size to 2gb but the transaction log still filled up. We've also noticed that the tblcheckoutlistitems table has over 1.7 million rows. Any idea what may be causing this?

Thanks,

Laurie

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Thu Jan 11, 2007 10:28 am

First on the large log issues, you can truncate the current logs and see if they continue to have problems with growing.

First, run backups:

BACKUP DATABASE { database_name | @database_name_var }
TO < backup_device > [ ,...n ]

Truncating the transaction log:

BACKUP LOG { database_name | @database_name_var }
{
[ WITH
{ NO_LOG | TRUNCATE_ONLY } ]
backup the log so the unused portion is removed ( BACKUP LOG command) and then run the following:

USE sgvault
GO

DBCC SHRINKFILE ( sgvault_log )
GO

lduresky
Posts: 20
Joined: Thu Mar 30, 2006 10:18 am

Post by lduresky » Thu Jan 11, 2007 10:34 am

The log has been truncated many times during the week or so we've had this problem and so far it has always filled back up.

Thanks,

Laurie

lduresky
Posts: 20
Joined: Thu Mar 30, 2006 10:18 am

Post by lduresky » Thu Jan 11, 2007 11:00 am

Any idea what might cause this?

Thanks,

Laurie

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Thu Jan 11, 2007 1:22 pm

Everytime someone does a checkout, a checkoutlist is created. Each checkoutlist has a list of all the items checked out.

A Checkoutlist stays in the database for 5 days (default), after which it is deleted. You can have thousands of checkoutlists. (We are making this much more efficient in the next Vault release, BTW)

It's possible to have millions of checkoutlist items if users did large checkouts and/or if the checkoutlists are not being cleaned up for some reason.

This eventually could resolve itself as the the checkoutlists from the big checkout get deleted. However, if the delete transaction doesn't complete (because the transaction log is filling up, for example), there's a backlog of checkoutlists and Vault keeps trying over and over to delete the checkoutlists.

If you continue to experience problems with this, email support at SourceGear.com attn Linda and we'll send you some queries to narrow down the problem.
Linda Bauer
SourceGear
Technical Support Manager

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Thu Jan 11, 2007 1:32 pm

How often are you backing up? I think the logs will be cleared when backed up.

Post Reply