Re: Problems getting LDAP to work:RE

Jochen Keutel (
Tue, 18 Jun 1996 12:27:56 +0200 (MESZ)


> Looks basically good to me, though I notice you are using ndbm.
> ndbm is known to be evil on many many platforms. You might try
> getting gdbm or berkeley db instead. I've seen ndbm fail in
> a bunch of nonobvious ways (mostly due to size restrictions).

this is also the experience I have. Just last week I tried to load
about 320 organizationalUnits via "ldapadd -f /tmp/all_ous" into
ndbm. (I use LDAP 3.3 on SINIX 5.42, machine ist RM600. (Risc))
I could load one country, one organization and 128 (interesting number, BTW)
organizationalUnits. The next ADD failed with operations error.
slapd says:
id2children_add( 2, 130 )
=> ldbm_cache_open( "//home2/ldap/ldapinst/ldap-3.3/ldbm_base/id2children.ndbm",
258, 600 )
<= ldbm_cache_open (cache 1)
<= id2children_add 0

id2children_add( 2, 131 )
=> ldbm_cache_open( "//home2/ldap/ldapinst/ldap-3.3/ldbm_base/id2children.ndbm",
258, 600 )
<= ldbm_cache_open (cache 1)
<= id2children_add -1 (idl_insert)
id2children_add failed

This happens indepenently on the number of attributes I create indexes for.

Are there any known limits for ndbm?

(The background is: We have a X.500 server with about 30000 entries.
I plan to use slapd as a "backup database" for our X.500 server. Once we have
switched all Windows clients to use LDAP to access the X.500 server it would
be very nice that we could start just slapd instead of ldapd if we get serious
problems with the X.500 server. Probably you'll recommend that we should
use gdbm or a self-written database backend in slapd ...
X.500 server is DIR.X 3.1 (SNI) which uses C-ISAM.)



Dr. Jochen Keutel currently at: Deutsche Telekom
duerr com-soft IZ Darmstadt

Phone: +49 6151 818 579

X.400 : /C=de/A=dbp/P=telekom400/O=dmst03/OU1=08/S=osys-02