Branko Čibej wrote:
> Wilfried Schmitten wrote:
>> I just updated from SuSE 9.1 to 9.3
>> the berkeley database changed from 4.2 to 4.3, all the new programs are
>> linked to that libraries.
>> From now, there is no access to the repository:
>> apache complains:
>> [Fri Apr 15 19:41:03 2005] [error] [client 192.168.211.165] (20014)Error
>> string not specified yet: Berkeley DB error while opening environment for
>> filesystem /work3/svn/repos/BEURON/db:\nDB_VERSION_MISMATCH: Database
>> environment version mismatch
>> svnadmin complains:
>> muemmel2:/work3/svn/repos/MUEMMEL # svnadmin verify .
>> svn: Berkeley DB error while opening environment for filesystem db:
>> DB_VERSION_MISMATCH: Database environment version mismatch
>> svn: bdb: Program version 4.3 doesn't match environment version
> Yes, well, that's to be expected.
>> and at last: svnadmin recover _destroyed_ the database
> I think you'd better show a listing of the <repostory>/db directory. I
> simply don't believe that your database was destroyed.
>> Yes, I have a backup... but what to do that the database is usable?
>> I tried some of the berkeley support utilities (db_stat, db_upgrade,
>> db_verify), but all of them complained mismatch of database version.
> http://www.sleepycat.com/docs/ref/am/upgrade.html, note the bold text.
> You _should_ be able to use db_upgrade to upgrade the database, but
> you'll also have to recompile SUbversion to get it linked against db43.
Actually, db_upgrade is not relevant in this scenario.
The relevant section of the BDB manual is:
If the application has a Berkeley DB transactional environment, and the log
files need upgrading but the databases do not, the application may be
installed in the field using the following steps:
1.. Shut down the old version of the application.
2.. Run recovery on the database environment using the DB_ENV->open method
or the db_recover utility.
3.. Remove any Berkeley DB environment using the DB_ENV->remove method or
an appropriate system utility.
4.. Archive the database environment for catastrophic recovery. See
Archival procedures for more information.
5.. Recompile and install the new version of the application.
6.. Restart the application.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Apr 16 00:46:18 2005