Keeping it on the list:
Begin forwarded message:
> From: David Bishop
> Date: 12. Juni 2005 08:08:50 MESZ
> To: Ryan Schmidt
> Subject: RE: Subversion 1.2 cannot read the older DB from previous
> version.
>
>
> On 12.06.2005, at 02:23, Ryan Schmidt wrote:
>
>> On 11.06.2005, at 19:55, David Bishop wrote:
>>
>>> I just updated Subversion (and TortoiseSVN) to 1.2.0. The install
>>> appeared to work correctly but I can no longer access the data base
>>> from the previous version.
>>> The Error Message received for a Commit is:
>>> Error: Commit failed (details follow):
>>> Error: Unable to open an ra_local session to URL
>>> Error: Unable to open repository 'file:///C:/SVN'
>>> Error: Berkeley DB error for filesystem C:/SVN/db while opening
>>> environment:
>>> Error: DB_VERSION_MISMATCH:
>>> Error: Database environment version mismatch
>>> Error: bdb: Program version 4.3 doesn't match environment version
>>>
>>> I cannot find any information on how to get the new version to read
>>> the older versions repository.
>>
>> The previous binary of Subversion for Windows was built with BDB 4.2;
>> the Subversion 1.2 binary for Windows was built with BDB 4.3. You
>> need to upgrade the repository to the new format. Instructions were
>> provided with the Subversion 1.2 Windows binary package. Read the
>> Read Me.
>
> Ryan,
> Thanks for the information. I think I got the repository converted
> but it
> didn't go like the FAQ says to do it. The following information may
> prove
> useful to others:
>
> In step one of the FAQ it says to run "svnadmin recover" which in my
> case
> reported the following:
>
> svnadmin recover C:\svn
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
> svnadmin: DB_RUNRECOVERY: Fatal error, run database recovery
> svnadmin: bdb: C:/svn/db\log.0000000055: log file open failed: No such
> file
> or directory
> svnadmin: bdb: PANIC: No such file or directory
> svnadmin: bdb: DB_ENV->log_put: 55: DB_RUNRECOVERY: Fatal error, run
> database recovery
>
> I took a leap of faith and tried " svnadmin recover svn" which seems
> to
> have created the very thing that was missing in the above failure,
> i.e. a
> new "log.0000000055" file showed up.
>
> I re-ran "svnadmin recover svn" and it reports the recovery was
> completed.
>
> C:\>svnadmin list-unused-dblogs svn
>
> C:\>svnadmin recover svn
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
>
> Recovery completed.
> The latest repos revision is 160.
>
> Again,
>
> Thanks for the information.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jun 12 12:44:08 2005