Re: berkley db files 4.2 -> 4.3

On May 20, 2005, at 10:22 AM, Stefan Kost wrote:
>
> When trying to commit, I get:
> OPTIONS request faild on '...'
> The OPTIONS request returned invalid XML in the response: XML parse
> error at line 1: no elemenr found (...)

This is a vague apache error, and is not necessarily related to the
'health' of your database at all.

To see if the database is healthy, try accessing it directly in one
of many ways:

    $ svnlook youngest /path/to/repos

    $ svnadmin lstxns /path/to/repos

    $ svn ls file:///path/to/repos

>
> Could somene please re-check it. It does not sound sane. After step
> 4 the repos is maybe usable by berkley db 4.2 again, but it still
> has not been updated to 4.3.

There's nothing in-sane about it. In order for 4.3 libraries to
access a 4.2 database, the only thing that needs to happen is for the
logs and shared-memory segments to be reset. That's the definition
of "update" in this case.

>
> Please, please just help people to use your product.

Are you somehow suggesting that nobody gets any tech support on this
list?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 20 19:03:13 2005