How to improve LDIF import performance in eDirectory 8.7

(Last modified: 05Jun2003)

This document (10083350) is provided subject to the disclaimer at the end of this document.

goal

fact

Novell eDirectory 8.7 for All Platforms

Importing thousands of users can take a lot of time regardless of the directory services product.

cause

Directory Service databases are customized databases. Unlike a standard database (IE Oracle, etc), directory services often times have many pre-configured features that require additional memory, processing power and disk space. eDirectory is no exception to this. The more the database writes (i.e. importing users through ldif files) can be optimized, the better import performance will be.

fix

eDirectory 8.7 has added a new feature to ICE imports. Before an object is added to eDirectory, all of the attributes on that object are compared against schema to verify whether or not they are valid. This is a very valuable test which will save a lot of time if there are errors. However, this feature can also damper performance because an additional check must be performed before the object is added.

Recommendation:
1. Create a sample LDIF that adds only unique objects. To explain further, if all of the objects being imported have the same attributes, only one record is required. If there are different types of objects in the same file, each unique object would need to be included.
2. Run the import and all eDirectory to verify schema.
3. After all errors are fixed, import the main ldif file into eDirectory adding the -C and the -n switches.

I.E. load ice.nlm -C -n -SLDIF -f users.ldif -DLDAP -s [servername] -p [ldap port] -d [DN] -w [pwd]

For additional information on eDirectory 8.7, please see the following solution. NOVL81742 - eDirectory 8.7 Readme Addendum

document

Document Title:	How to improve LDIF import performance in eDirectory 8.7
Document ID:	10083350
Solution ID:	NOVL89624
Creation Date:	19May2003
Modified Date:	05Jun2003
Novell Product Class:	Novell eDirectory

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.