8.6 Limitations

This section contains limitations of the ldif2dib utility:

8.6.1 Schema

  • The LDIF file should mention all the object classes that an entry belongs to. An entry can belong to multiple object classes because of inheritance. For example, an entry of type inetOrgPerson should have following syntax in the LDIF file:

    objectclass: inetorgperson
    objectclass: organizationalPerson
    objectclass: person
    objectclass: top
  • Currently, following syntaxes are not supported:











8.6.2 ACL Templates

ACLs that are specified in the ACL templates for an object class, are not automatically added for objects bulkloaded using ldif2dib.

8.6.3 Options

On Linux, if the -b option is used, the screen that displays statistics disappears after the bulkload is complete. The final statistics, however, are written to the log file for reference.

8.6.4 Simple Password LDIF

On Windows, while uploading LDIF having simple password, ldif2dib might fail if the NICI keys in system and Administrator folder are not in sync. To work around this issue, access the keys present in the nici/system folder as follows:

  1. Go to the C:\Windows\system32\novell\nici\folder.

  2. Backup the files present in the Administrator folder.

  3. Get access to the system folder and its files by following the below mentioned steps:

    1. Go to the Security tab in the Properties window of the system folder.

    2. Select Advanced Options and go to Owner tab.

    3. Select Administrator.

    4. Go back to the Security tab and add Administrator to the list.

      Repeat the similar steps to get read access to all the files present inside the system folder.

  4. Overwrite the files in the Administrator folder with the ones in the system folder.

  5. Once the upload is done, copy the backed up files to the Administrator folder.

  6. Revert back the Administrator's access to the system folder and also the files within the folder.

8.6.5 Custom Classes

Bulkloading an LDIF with a large number of container objects using ldif2dib can result in a memory build up leading to a -150 error being reported.