Red Hat 8.1, Справочник по командам

Страница: 295 / 372

db2index (Reindexes Database Index Files)
281
Option Description
-M Uses multiple files for storing the output LDIF,
with each instance stored in
instance filename
(where
filename
is the filename specified for
-a
option).
-n
backendInstance
Gives the instance to be exported.
-N Specifies that the entry IDs are not to be included
in the LDIF output. The entry IDs are necessary
only if the
db2ldif
output is to be used as input
to
db2index
.
-r Exports the information required to initialize a
replica when the LDIF is imported. Using this
option requires that the server be stopped first,
then run the
db2ldif
command.
The LDIF file which is created with
db2ldif
can
be imported using
ldif2db
. When it is imported,
if the
-r
option was used, than the database is
automatically initialized as a replica.
See
Section 7.3.8, “ldif2db (Import)”
for
information on importing an LDIF file.
-s
suffix_name
Names the suffixes to be included or the
subtrees to be included if
-n
has been used.
-u Requests that the unique ID is not exported.
-U Requests that the output LDIF is not folded.
-x
suffix_name
Names the suffixes to be excluded.
Table 7.6. db2ldif Options
7.3.5. db2index (Reindexes Database Index Files)
Reindexes the database index files. Ellipses indicate that multiple occurrences are allowed.
For information on the equivalent Perl script, see
Section 7.4.4, “db2index.pl (Creates and Generates
Indexes)”
.
Syntax
db2index
[[ -n
backendInstance
] | [ -s
includeSuffix
]] [ -t
[
attributeName{:indextypes(:mathingrules)}
] ] [ -T
vlvAttribute
]
Usage
Here are a few sample commands:
• Reindex all the database index files:
db2index
• Reindex
cn
and
givenname
in the database instance
userRoot
: