Ah, ok.

It's just that I'm installing a new server, and I have to import an ldbm database and I want to use dbd backend instead I thought I had to convert it to the dbd format.

Thanks.

2007/3/1, Quanah Gibson-Mount quanah@stanford.edu:

--On Thursday, March 01, 2007 7:41 PM +0000 Net Warrior netwarrior863@gmail.com wrote:

...

Hi there guys.

I was just wondering if there is a tool to convert an ldbm database to the new bdb backend.

bdb is not new, it has existed since the OpenLDAP 2.1 release.

The general tool one uses is "slapcat" to export the database into LDIF format, and then "slapadd" to import the database from the LDIF file.

--Quanah

-- Quanah Gibson-Mount Principal Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

Thanks for your help..

2007/3/1, Asrai khn asraikhn@gmail.com:

On 3/2/07, Net Warrior netwarrior863@gmail.com wrote:

...

Hi there guys.

I was just wondering if there is a tool to convert an ldbm database to the new bdb backend.

HI, I duno about any tools but its very easy to migrate from idbm to back-bdb if you search the archives of few days back you will find a thread in which it was discussed, and i had successfully migrated our openldap to back-dbd.

here is the short summary of steps for this..

Migrate to BDB or HDB. Here's the rough idea: shutdown slapd slapcat -f /path/to/slapd.conf -l mydb.ldif vi /path/to/slapd.conf Change your database to a new directory. Read about tuning, cache sizing, and other stuff. Read openldap man pages. Read oracle's tuning docs for bdb. Re-Read openldap man pages. :wq slapadd -f /path/to/slapd.conf -l mydb.ldif

Fix permissions on /var/run so the slapd user can write there -- this one is pretty easy restart slapd