I remember like seeing similar error.
Then we dumped strings table alone using db_dump and loaded it back
using db_load, it seemed to have fixed our problem.
May be you can try it.
$db_dump strings >/tmp/strings.dmp
$mv strings _strings.old
$db_load -f /tmp/strings.dmp strings
$svnadmin recover
All the best.
With regards
Kamesh Jayachandran
Jordi Vilalta wrote:
> Hi,
>
> 2006/9/19, Kamesh Jayachandran:
>> Probably your bdb repos could have got corrupted.
>> Try svnadmin recover.
>> If it does not work, 'svnadmin dump' and load the repo in to
>> someother repo.
>> If that also don't work, try repairing catastropic db_recover on strings
>> table.
>
> Thanks for your fast answer. Here's the result:
>
> $ svnadmin recover .
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
>
> Recovery completed.
> The latest repos revision is 811.
> $ svnadmin dump . > dump
> * Dumped revision 0.
> svn: No such string '6e'
> $ db4.2_recover -vech db
> db_recover: Finding last valid log LSN: file: 49 offset 642600
> $ svnadmin verify .
> * Verified revision 0.
> svn: No such string '6e'
>
> It seems like it's doing nothing. Am I doing something wrong? Thanks
> for your support.
>
> Regards,
>
> Jordi Vilalta
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 19 15:52:38 2006