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

Re: Database upgrade problem

From: John Szakmeister <john_at_szakmeister.net>
Date: 2007-01-09 14:13:40 CET

----- Greg Adam <gadam@lancashiredigital.com> wrote:
> John Szakmeister wrote:
> > IIRC, using any BDB prior to 4.3, you could just run 'svnadmin
> > recover' on the repository. With 4.3 or better, I believe you
> had
> > to simply remove the environment, and the unused log files. Ah,
> > here's mention of it in the FAQ:
> > http://subversion.tigris.org/faq.html#bdb43-upgrade
> >
> > -John
> Thanks for this, although I still can't get it to work. I currently
> have BDB
> 4.2(.52) installed, but when I run 'svnadmin recover' I get the
> following
> error:
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
> svn: bdb: Ignoring log file:
> /repositories/management/db/log.0000000016:
> unsupported log version 10
> svn: bdb: Invalid log file: log.0000000016: Invalid argument
> svn: bdb: PANIC: Invalid argument
> svn: bdb: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
> Any ideas?

Unfortunately no. :-( I haven't used bdb in a while. Have you tried using the db_dump commands to dump each of the tables?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 9 14:14:01 2007

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.