Jean-Marc van Leerdam wrote:
> 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.
If you're lazy, you can also use the new binaries and first 'svnadmin
recover' (will print an error) and after that 'svnlook youngest'. It
will also work, but keep a backup handy just in case. The safe way to
do it is of course the above.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu May 26 14:29:25 2005