Skip Navigation Links | |
Exit Print View | |
Oracle Directory Server Enterprise Edition Man Page Reference 11g Release 1 (11.1.1.5.0) |
- creates a filtered version of an LDIF input file
install-path/bin/fildif -i input-file [-o output-file] [-f ] -b repl-agmt-dn -p instance-path
The fildif command creates a filtered version of an LDIF input file. fildif takes a configuration file as an input parameter. This configuration file must conform to the configuration rules of the filtering service included as part of Directory Server, and must contain the specific set and element entries that define these rules. The configuration rules can be defined by using Directory Service Control Center or at the command-line.
fildif does not require the Directory Server instance to be running.
A filtering service configuration is accessed through a replication agreement. The replication agreement entry DN is provided to fildif with the -b option.
Note - fildif does not support the LDIF input file bigger than 2GB.
The following options are supported:
The DN of the replication agreement used as the filtering service configuration entry point. The entry specified must exist in the configuration of the Directory Server instance.
Force fildif to overwrite the contents of the specified output file, if it exists.
The input LDIF file whose contents are filtered.
The output LDIF file in which the filtered results are stored. If no output file is specified, the default output file is ./output.ldif.
The full path to the Directory Server instance whose configuration contains the replication agreement specified as a parameter of the -b option.
Example 1 Using All Options
The following example shows the fildif command to generate an output file filt_data.ldif that overwrites the file if it exists already.
$ fildif -i data.ldif -o filt_data.ldif -f \ -b "cn=ds.example.com:389,cn=replica,cn=dc=example\,dc=com,\ cn=mapping tree,cn=config" -p /local/dsInst
The following exit values are returned:
Successful completion.
An error occurred.
On error, verbose error messages are output to standard output.
See attributes(5) for descriptions of the following attributes:
|