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

Re: Problems accessing repositories after migration to new server

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-08-26 19:50:53 CEST

On Aug 26, 2006, at 13:41, Kevin Turner wrote:

> Phew, I was getting worried. Since the Apache error log says (20014)
> Error string not specified yet: Berkeley DB error for filesystem D:\
> \SVN/equibook/db while opening environment:\nDB_VERSION_MISMATCH:
> Database environment version mismatch
>
> I am sure you are right.
>
> Can I svmadmin dump all the repositories in one go or do I have to
> do them all individually? We have a large number of repositories.

You must dump one repository at a time. You can probably write a
small script to automate it if you have that many.

> I am curious as to how I will have acquired a newer version of BDB
> on the new server though. It is basically a Swing Migration so the
> software "should" be the same.

I don't know what a "swing migration" is but it certainly appears
that, through whatever means, you have a different version of BDB on
the new machine. You can perform some steps to upgrade the repository
to the new BDB version; the FAQ has some instructions:

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

But I personally recommend the dump-and-load strategy and migration
to FSFS. Many people have reported problems with BDB repositories,
and only a few have reported problems with FSFS. Though many people
also have success with BDB, I personally choose not to take the chance.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Aug 26 19:52:07 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.