NAME | SYNOPSIS | DESCRIPTION | OPTIONS | NOTES | EXIT STATUS | ATTRIBUTES | SEE ALSO
The ldif2db command imports directory contents from LDIF. To run this tool Directory Server must be stopped.
The following options are supported:
File name of the input ldif file(s). When you import multiple files, they are imported in the order in which you specify them on the command line.
Name of database to be imported. Ensure that you specify a database name that corresponds to the suffix contained by the LDIF file. Otherwise the data contained by the database is deleted and the import fails.
Requests that only the core database is created without attribute indexes.
Suffixes to be included. If used in conjunction with the -n option, this option specifies the subtree(s) to be included. When importing suffixes split across multiple backends, you must import each subsuffix separately. With the -s suffix option, Directory Server imports only those entries in the backend containing the suffix entry.
Suffix(es) to be excluded.
Specifies the file in which the password for the key database is held, also used when handling encrypted attributes.
Specifies the password for the key database, providing a means of authentication required by Directory Server when handling encrypted attributes.
ldif2db supports LDIF version 1 specifications. You can load an attribute using the:<URL specifier notation. For example:
jpegphoto:< file:///tmp/myphoto.jpg
Although the official notation requires three ///, the use of one / is tolerated.
The default behavior of a read-write replica that has been initialized either online or offline from a backup or an LDIF file, is NOT to accept client update requests. The replica will remain in read-only mode and refer any updated operations to other suppliers in the topology until the administrator does one of the following:
changes the duration of the read-only mode default period using the ds5referralDelayAfterInit attribute
manually resets the server to read-write mode using the ds5BeginReplicaAcceptUpdates attribute (once the replica has completely converged with the other supplier in the topology)
The second option is advised because it does not present non-convergence risks.
You must specify either the -n or the -s option (or both), and the -i option. When identifying hosts, you must use either symbolic names or IP addresses for all hosts. Using a combination of the two can cause problems.
The following exit values are returned:
Successful completion.
Otherwise check logs for further information.
See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
---|---|
Availability | SUNWdsvu |
Stability Level | Committed Private |
directoryserver(1M), ldif2db-task(1M), ldif2db.pl(1M), db2ldif(1M), mmldif(1), start-slapd(1M), stop-slapd(1M), restart-slapd(1M)
NAME | SYNOPSIS | DESCRIPTION | OPTIONS | NOTES | EXIT STATUS | ATTRIBUTES | SEE ALSO