On 12/09/2014 05:58 PM, Fong, Trevor wrote:
Hi Mark,
I’ve afraid adding nsIndexIDListScanLimit to cn=objectclass,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config doesn’t seem to have any effect. Did this:
dn:
cn=objectclass,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config
changetype: modify
add:
nsIndexIDListScanLimit
nsIndexIDListScanLimit:
limit=-1 type=eq values=inetOrgPerson
Hmm that's very strange, try this:
dn: cn=objectclass,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config
changetype: modify
replace: nsIndexIDListScanLimit
nsIndexIDListScanLimit: limit=-1 type=eq values=inetOrgPerson
nsIndexIDListScanLimit: limit=-1 type=eq flags=AND values=inetOrgPerson
Also, is userRoot the mapping tree that refers to your "dc=<your dc>"? I just want to make sure we are updating the correct objectclass index configuration entry.
This should get rid of those unindexed searches. Is there anything in the 389 DS errors log regarding these settings?
Thanks,
Mark