[Date Prev][Date Next]
Database corruption with ldbm backend (ITS#935)
Full_Name: Matthias Ohlemeyer
Submission from: (NULL) (126.96.36.199)
When updating a few hundred entries in my LDAP-Database I somehow manage to
corrupt my backend database files (gdbm under SuSE 7.0), at least that's what I
think is going on.
I have a small commandline Java-Program using JNDI that finds the entries by uid
und updates a few attributes. When I interrupt the running Program whith Ctrl-C
(the client-programm runs on a Windows machine) I sometimes get a very strange
situation in the database. Certain entries can only be found when specifying
objectclass=top although, when viewing the entry, other objectclasses are also
Using filter (&(objectclass=inetorgperson)(uid=abc12)) the entry is not found,
using filter (&(objectclass=top)(uid=abc12)) the entry is found.
The entry looks like this
dn: uid=abc12, o=AB, dc=ABCD, dc=de
cn: xyz qwe
The strange thing is, that I could find the entry before running the Java
program and I can find the entry, when the programs terminats normally. I tried
using slapindex, but this did not help. On the other hand I got it fixed, when I
do an LDIF-Export of all entries, delete all entries an do an LDIF-import
Is this an openldap or a gdbm related problem. Do you think switching to
sleepycat would help?