[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] Error using 1.2 nightly on local 1.1 repository

From: Jean-Marc van Leerdam <developer_at_bemy.demon.nl>
Date: 2005-05-24 21:48:15 CEST

Hi Mark,

> Jean-Marc van Leerdam <developer@bemy.demon.nl> wrote on 05/24/2005
> 03:24:25 PM:

>> Hi All,
>>
>> Sorry if this is a FAQ, but:
>>
>> I was under the impression that all 1.x SVN repositories should be
>> accessible by TSVN 1.2, but for my local repo this is not the case.
>> THe following errors are shown when doing an update of my WC's:
>>
>> Fout: Unable to open an ra_local session to URL
>> Fout: Unable to open repository 'file:///C:
>> /Data/develop/svn/translations/TortoiseSVN/trunk'
>> Fout: Berkeley DB error for filesystem C:/Data/develop/svn/db while
> opening
>> environment:
>> Fout: DB_VERSION_MISMATCH:
>> Fout: Database environment version mismatch
>> Fout: bdb: Program version 4.3 doesn't match environment version

> file:// protocol would probably be the exception to this. Subversion 1.2
> uses BDB 4.3 so you need to do some minor updates to your BDB repositories
> to use them from 1.2.

> See this FAQ:

> http://subversion.tigris.org/faq.html#bdb43-upgrade

Yep, that did the trick:

After upgrading to Berkeley DB 4.3, I'm seeing repository errors.

Normally one can simply run svnadmin recover to upgrade a Berkeley DB
repository in-place. However, due to a bug in the way this command
invokes the db_recover() API, this won't work correctly when upgrading
from BDB 4.0/4.1/4.2 to BDB 4.3.

Use this procedure to upgrade your repository in-place to BDB 4.3:

    * Make sure no process is accessing the repository (stop Apache,
      svnserve, restrict access via file://, svnlook, svnadmin, etc.)
    
    * Using an older svnadmin binary (that is, linked to an older BerkeleyDB):
         1. Recover the repository: 'svnadmin recover /path/to/repository'
         2. Make a backup of the repository.
         3. Delete all unused log files. You can see them by running
            'svnadmin list-unused-dblogs /path/to/repeository'
         4. Delete the shared-memory files. These are files in the
            repository's db/ directory, of the form __db.00*

The repository is now usable by Berkeley DB 4.3.

Steve: is there any way one can do this without the CL client?

Regards,

Jean-Marc

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue May 24 21:48:36 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.