svn: database is locked, executing statement 'RELEASE s0'

R

15

23

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?

Roark answered 16/7, 2012 at 8:55 Comment(3)

This may mean that your working copy is accessed by another client at the same time. – Acrocarpous 16/7, 2012 at 10:22

But I usually ensure that I've closed down all tortoise SVN client windows except the window I'm using to initiate the merge? – Roark 16/7, 2012 at 13:36

Run cleanup using break write locks. It should work. – Untrimmed 1/3 at 13:50

V

12

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

Villar answered 29/11, 2013 at 13:6 Comment(1)

Thanks, I had tried Clean Up without "Refresh Shell Overlays" checked and that was not sufficient - checking that box allowed Clean Up to do the right thing and unblock my Merge/Reintegrate command. – Oceania 14/8, 2018 at 18:46

H

9

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

Huskamp answered 18/2, 2014 at 11:6 Comment(1)

Thanks a lot! I have this problem since so long and it was because I had Netbeans open when doing update. – Rottweiler 14/11, 2016 at 13:27

K

7

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.

Kindly answered 16/10, 2013 at 13:21 Comment(0)

V

6

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.

Volute answered 16/7, 2012 at 19:23 Comment(1)

I had to kill the svn process in the shell too. – Mercuric 7/8, 2012 at 5:59

K

6

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

Kirst answered 6/4, 2017 at 21:52 Comment(1)

This helps, and is quicker than restarting Netbeans. – Rms 30/5, 2017 at 18:30

T

3

Do SVN clean up. Problem will be resolved.

Telegenic answered 3/10, 2013 at 4:54 Comment(1)

Actually it is not resolved. Being over-confident ruins credibility. Better to allow for the possibility there can be difference causes/solutions for the same symptoms in many cases. – Propitious 11/6, 2020 at 16:2

A

2

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.

Aeonian answered 24/7, 2013 at 18:15 Comment(0)

D

2

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

Duval answered 20/2, 2017 at 17:36 Comment(0)

B

1

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

Bake answered 5/11, 2015 at 4:25 Comment(0)

R

0

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.

Roark answered 16/7, 2012 at 23:4 Comment(0)

E

0

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

Eunuchize answered 25/9, 2013 at 7:21 Comment(0)

H

0

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.

Horologium answered 22/8, 2017 at 11:37 Comment(1)

You should upgrade to the latest SVN 1.9.x – Augustaaugustan 22/8, 2017 at 17:26

U

0

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.

Unwind answered 10/9, 2019 at 14:46 Comment(0)

C

0

I faced the same issue. For me, it was because the project folder was inside OneDrive and OneDrive was syncing the same folder. When I stopped syncing OneDrive and closed it, things were resolved.

Recommended topics

Hot tags