Re: Server "commit"

[Clif H. <cl...@di...>]

> 
> hello,
> 
> We're loading LDAP entries to iPlanet 4.1 Directory Server via Net::LDAP
> v 0.22 using perl v5.6.0.
> 
> We can successfully read/modify/add/delete, a very good start.
> 
> However, we need to add on the order of 20k+ records. If all records are
> attempted at the same time, the "journal" logs fill the hard drive after
> about 400 additions. We can consistently add about 300 records, after
> which we must exit the script and wait a few moments before running the
> next batch. We wish to ultimately have a hands off one-shot process.
> 
> I've looked at the server configuration, perhaps to turn off
> "journaling" temporarily, but have not seen anything promising yet.
> 
> Is there a way to "commit" the changes in progress from the perl script?
> Having the script pause and/or unbind does not seem to do it.
> 
>    thanks,
>    Gordon Smith
> 
> 

I have loaded 60K+ plus records on my Netscape 4.x directory server
using a script that does almost exactly what you describe.

The script binds, loads 250 records, unbinds, sleeps 2 minutes,
and then repeats this process until all records have completed. 
To the user this looks like one "long" continuos process.

There is a bulk loading script for Netscape servers that bypasses
ldap, you might want to look into using it.  I have never used it but
I have been told it is very fast and works quite well.  It comes with
the Netscape server software.

This is a problem that is not unique to Netscape, I have had this 
problem on 2 other directory servers also.  How sever the problem is
depends on computer speed, computer load, and amount of available
ram and disk space. 

Clif Harden           INTERNET:  c-h...@ti...