23
votes

I keep getting the error listed blow in attempting a merge from a private branch:

database is locked, executing statement 'RELEASE s0'

I run collabnet subversion edge server: 1.7.5-3220.94

I run the tortoise svn client: TortoiseSVN 1.7.7, Build 22907 - 64 Bit , 2012/05/15 12:16:05

Can anyone please point me to what's causing this, and how to resolve this. The references on the Web suggest some process is using the sqlite backend. The generic "Release lock" action from svn client contextual menu doesn't seem to help?

14
This may mean that your working copy is accessed by another client at the same time.Dmitry Pavlenko
But I usually ensure that I've closed down all tortoise SVN client windows except the window I'm using to initiate the merge?Terman

14 Answers

12
votes

If you're on Windows version just let's do the next:

Right click on the repo folder and go to TortoiseSVN options and next to this select the option Clean Up.

In clean up's options select:

Clean Up working copy status
Refresh Shell Overlays
Include external

sho

8
votes

I had the same problem. I was using Tortoise and Eclipse at the same time. Closing Eclipse resolved this issue.

7
votes

I got this error when I tried to update local copy but merge window was left open. I closed the merge window and update and cleanup worked correctly.

6
votes

If I open a shell and run a subversion command then try to merge using Tortoise I get this error.

Closing the shell window and then doing the merge again from Tortoise it works.

6
votes

IF you use another program (netbeans) , you have configure the program Netbeans :

options > Team > versioning > subversion > Preferential client Alter this option for "CLI", and after select the SVN.exe in the dir TortoiseSVN\BIN

this resolve the problem the locked database

4
votes

Do SVN clean up. Problem will be resolved.

2
votes

I've had a friend that got stuck with this. He restarted his computer and everything went fine, nothing lost and he could work again.

1
votes

If nothing work from the above answers then just kill the process from task manager and try it again. No need to restart. It works for me

1
votes

This usually happens because another program is performing version control on the same working copy.

Close the program (Eclipse, Netbeans, ...), and try again, after performing a "Clean Up" on the working copy

0
votes

Thanks everyone. I think it's likely a case that my working copy had local modifications. I just skimmed through TortoiseSVN 1.7 By: Lesley A. Harrison which recommends that to ensure a smooth merge: ensure your working copy is clean and has no local modifications. I think this wasn't the case in my instance.

cheers.

0
votes

use lsof to list svn's file handle and kill it then run svn cleanup

0
votes

This helped me solve the problem (subversion 1.7.10):

 $ cd /my/repository/.svn
 $ mv wc.db wc.db.old
 $ sqlite3 wc.db.old
 sqlite> .backup main wc.db
 sqlite> .exit

After making sure it works, you can remove wc.db.old.

0
votes

On Linux, the first thing to check is if any other "svn update" is in progress or not. If yes, either wait for it to finish or kill it(if you killed it, you will need to run "svn cleanup"). After this, svn should behave normally.

-1
votes

On Windows 2008 R2, a OS restart fixed it.