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

Re: Upgrading Berkeley DB 4.0 to ... 4.2

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-03-12 02:11:34 CET

"Kay Abendroth" <abendroth@wsc-gmbh.de> writes:

> > Generally this boils down just making sure you have removed all
> > unused log files, and then running recover. If you have lingering
> > logfiles, they can get in the way of the upgrade process.
>
>
> What are lingering logfiles and how do I find out I have them (or
> not)?

I guess that was a bad choice of words. IIRC, you essentially want to
do this:

   $ /path/to/Berkeley40/bin/db_recover -ve /path/to/repos/db
   $ /path/to/Berkeley40/bin/db_archive -h /path/to/repos/db | xargs rm
   $ /path/to/Berkeley42/bin/db_recover -ve /path/to/repos/db

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 12 02:12:46 2004

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