Re: bdb_index_read: failed (-30990)

[Ace Suares <ace@suares.nl>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Tony wrote:
>
> My experience is, that it doesn't matter whatever - if any attribute is
> queried at all, then index it, even if the parameter is only 'pres'. I
> have a list of indexes as long as your arm (that's how I found out how
> to use vi's fantastic macro feature) - half of them are never even
> queried, but I don't get any corruption issues any more.
>
> > Some questions:
> >
> > Do I need to index every attribute that is used in a filter ?
>
> Definitely.


My own research shows that it's not needed - without that attribute indexed, 
the software runs fine on my SuSE box but not on my Debian box.

> > Is it really necessary to index a two-value attribute ?
>
> Definitely.

So, not so definetely.

> > Why is the problem intermittent ?
>
> You wrote that the problem only occurs on Debian. It could be anything -
> compiler, glibc, clib, other libraries. There's an enormous difference
> between RH distros, even, for the above reasons.

So, I am now at the point where I believe the problem can only be traced down 
to differences in SuSE 8.2 and Debian Woody. But how to find out what the 
problem is ? I tried OL 2.1.25 and 2.2.4, And with 2.1.25 I tried bdb 4.2.52, 
ldbm/dbd, and ldbm/gdbm. All the same results. 2.2.4 is compiled with 4.2.52.


How to find out if it's glibc ? Or the compiler ?
The logs don't tell me anythinjg that I can relate to.

Cheers,
ace

site: http://www.suares.nl * http://www.qwikzite.nl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/+DGxy7boE8xtIjURAv2MAJ0XZFtyRFdS9z4Hl70MetTcdJ/VKQCeLWef
TBySsHnjaZbDnQph451gmdo=
=azFg
-----END PGP SIGNATURE-----