Wilfried Schmitten wrote:
> Moin,
> 1. I didn't know about migrations across BDB versions and so I run into
> this
> desaster.
> 2. Thank you to some people, who tried to help.
> 3. the statement, svnadmin destroyed the database was wrong. There was a
> message "panic" and after that I saw that the files __db.* were deleted.
> So
> I thought, if something can go wrong it will ;-)
> 4. The almost solution (there is still an error) till now:
> a) I copied the files to my laptop running the old libraries and made
> "db_dump file -f file" on all files that are listed by "db_archive -s".
> b) On the server I deleted __db.* and log.* and copied the files from the
> laptop to the server.
> c) with "db_load -f file file" I produced a new database (is that
> correct?)
Perhaps. There are easier ways, but the basic procedure is valid,... EXCEPT
At steps b/c) - are you saying that you did a db_load with the files
(changes copies transactions revisions uuids representations strings nodes)
still existing?
If so, this is likely the cause of the "Invalid change ordering" error you
quote below.
Delete __db.* log.* AND *s
Then redo your db_load commands.
> Now:
> I get a correct message, if I use ra_local as user root, all revisions
> are
> listed when I use "svn log file:///work3/svn/repos/BEURON/"
But, does "svnadmin verify" work?
> Trying this via http, something goes wrong (sorry, some messages are in
> german):
>
> wshbg_at_muemmel2:~/BEURON> svn log http://muemmel2/repos/BEURON
...
> and in apache err_log I find:
> [Sun Apr 17 20:51:14 2005] [error] [client 192.168.211.164] Invalid change
> ordering: non-add change on deleted path [400, #160004]
Responded to above.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Apr 17 23:14:43 2005