RE: scope not ok errors on very large databases (ITS#3343)

[Armbrust.Daniel@mayo.edu]

Followup to the last post - when I reloaded my problematic database on openldap 2.2.17 using these parameters:

#define BDB_IDL_DB_SIZE         (1<<17) /* 64K IDL on disk - dan modified to 128K */
#define BDB_IDL_UM_SIZE         (1<<18) /* 128K IDL in memory - dan modified to 256K*/

The problem that I reported in the initial post went away.  I am now able to view/search, etc, on this large node in my database.  This surprised me, because I didn't think that I had increased the size of the key enough to fix the problem.  It must be because my ~260,000ish entries are being split across multiple keys (I'm not sure why, the are almost all aliases)

Am I likely to run into any other problems by using these larger values?  If not, is there a reason not to update openldap itself to use these larger values?

Thanks,

Dan