RE: "ldapsearch uid=ab*" works "ldapsearch cn=a*" doesn't in 2.1 .19

["Harms, Hendrik (TOJAQ)" <extern.hendrik.harms@volkswagen.de>]

I got the same problem on my openldap-2.1.19 / berkeley-db-4.1.25
I've exported the whole data of my 2.1.17 with ldapsearch and imported then
with ldapadd 
into the 2.1.19. Searching one character on an index still doesn't work. It
returns 
no value but this very quick.

Hendrik Harms
Tojaq Datentechnik

> -----Original Message-----
> From:	Michael Dean [SMTP:sysmwd@detir.qld.gov.au]
> Subject:	RE: "ldapsearch uid=ab*" works  "ldapsearch cn=a*" doesn't
> in 2.1.19
> 
> I forgot to mention that I removed the 2.1.17 raw database files and
> re-populated the empty database of the new 2.1.19 server with an ldif made
> from the old 2.1.17 server. Should the format change problem still cause
> me a problem?
> 
> 
> On Tue, 13 May 2003, Howard Chu wrote:
> 
> > > -----Original Message-----
> > > From: owner-openldap-software@OpenLDAP.org
> > > [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Michael Dean
> >
> > > hi
> > >
> > > I've just recently upgraded from 2.1.17 to 2.1.19 and I'm now having
> > > problems
> > > doing a one character plus wildcard search in 2.1.19.. ie.
> > >
> > > with two characters (or more) with the wildcard the search
> > > returns some
> > > data ...
> >
> > Due to a bug in substring indexing that was fixed in 2.1.18 and 2.1.19,
> the
> > substring index format changed. You need to run slapindex to regenerate
> your
> > substring indexes. Sorry for this, the format change was unavoidable in
> order
> > to correct the bug.
> >