1LDIF2DB.PL(8) System Manager's Manual LDIF2DB.PL(8)
2
3
4
6 ldif2db.pl - Directory Server perl script for importing a LDIF file
7
9 ldif2db.pl -n backend [-Z serverID] [-D rootdn] { -w password | -w - |
10 -j filename } [-P protocol] {-s includeSuffix}* [{-x excludeSuffix}*]
11 [-O] [-c chunksize] [-h] [-g [string]] [-G namespace_id] {-i filename}*
12
14 Imports LDIF file(s) into the server. Either the option '-n' or '-s'
15 must be used. This script creates an entry in the directory that
16 launches this dynamic task.
17
19 A summary of options is included below:
20
21 -Z Server Identifier
22 The server ID of the Directory Server instance. If there is
23 only one instance on the system, this option can be skipped.
24
25 -D Root DN
26 The Directory Manager DN, or root DN. If not specified, the
27 script will search the server instance configuration for the
28 value.
29
30 -w password
31 The rootdn password.
32
33 -w -
34 Prompt for the rootdn password.
35
36 -j password filename
37 The name of the file that contains the root DN password.
38
39 -n Backend Name
40 The name of the LDBM database to restore. Example: userRoot
41
42 -s includeSuffix
43 Specifies the suffixes to be included or specifies the subtrees
44 to be included.
45
46 -x excludeSuffix
47 Specifies the suffixes to be excluded or specifies the subtrees
48 to be excluded.
49
50 -i filename
51 Name for the LDIF file to import.
52
53 -g [string]
54 Generates a unique ID. Type none for no unique ID to be gener‐
55 ated and deterministic for the generated unique ID to be name-
56 based. By default, a time-based unique ID is generated. When
57 using the deterministic generation to have a name-based unique
58 ID, it is also possible to specify the namespace for the server
59 to use, as follows:
60
61 -g deterministic namespaceId
62
63 namespaceId is a string of characters in the format 00-xxxxxxxx-
64 xxxxxxxx-xxxxxxxx-xxxxxxxx.
65
66 -G namespace_id
67 Generates a namespace ID as a name-based unique ID. This is the
68 same as specifying the -g deterministic option.
69
70 -P Protocol
71 The connection protocol to connect to the Directory Server.
72 Protocols are STARTTLS, LDAPS, LDAPI, and LDAP. If this option
73 is skipped, the most secure protocol that is available is used.
74 For LDAPI, AUTOBIND is also available for the root user.
75
76 -O
77 Requests that only the core database is created without
78 attribute indexes.
79
80 -c Chunk size
81 The number of entries to process before starting a fresh pass
82 during the import. By default this is handled internally by the
83 server.
84
85 -h
86 Display usage
87
89 ldif2db.pl -Z instance1 -n userRoot -i /LDAP/ldif/data.ldif
90
91 ldif2db.pl -s "dc=example,dc=com" -i /LDAP/ldif/data.ldif -D 'cn=direc‐
92 tory manager' -w password -P STARTTLS
93
94 Note: security must be enabled to use protocol STARTTLS. If
95 STARTTLS is not available it will default to next strong‐
96 est/available protocol automatically.
97
99 Exit status is zero if no errors occur. Errors result in a non-zero
100 exit status and a diagnostic message being written to standard error.
101
103 ldif2db.pl was written by the 389 Project.
104
106 Report bugs to https://pagure.io/389-ds-base/new_issue
107
109 Copyright © 2017 Red Hat, Inc.
110
111
112
113 March 31, 2017 LDIF2DB.PL(8)