1 .TH SLAPSCHEMA 8C "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2009 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slapschema \- SLAPD in-database schema checking utility
26 is used to check schema compliance of the contents of a
29 It opens the given database determined by the database number or
30 suffix and checks the compliance of its contents with the corresponding
31 schema. Errors are written to standard output or the specified file.
32 Databases configured as
34 of this one are also output, unless \fB-g\fP is specified.
36 Administrators may need to modify existing schema items, including
37 adding new required attributes to objectClasses,
38 removing existing required or allowed attributes from objectClasses,
39 entirely removing objectClasses,
40 or any other change that may result in making perfectly valid entries
41 no longer compliant with the modified schema.
43 .B slapschema tool after modifying the schema can point out
44 inconsistencies that would otherwise surface only as soon as
45 inconsistent entries need to be modified.
48 The entry records are checked in database order, not superior first
49 order. The entry records will be checked considering all
50 (user and operational) attributes stored in the database.
51 Dynamically generated attributes (such as subschemaSubentry)
52 will not be considered.
56 Only check entries matching the asserted filter.
60 "(!(entryDN:dnSubtreeMatch:=ou=People,dc=example,dc=com))"
62 will check all but the "ou=People,dc=example,dc=com" subtree
63 of the "dc=example,dc=com" database.
66 Use the specified \fIsuffix\fR to determine which database to
67 check. The \-b cannot be used in conjunction
73 Enable continue (ignore errors) mode.
76 Enable debugging messages as defined by the specified
83 Specify an alternative
88 specify a config directory.
93 are specified, the config file will be read and converted to
94 config directory format and written to the specified directory.
95 If neither option is specified, an attempt to read the
96 default config directory will be made before trying to use the default
97 config file. If a valid config directory exists then the
98 default config file is ignored.
101 disable subordinate gluing. Only the specified database will be
102 processed, and not its glued subordinates (if any).
104 .BI \-l " error-file"
105 Write errors to specified file instead of standard output.
108 Check the \fIdbnum\fR\-th database listed in the
109 configuration file. The config database
110 .BR slapd-config (5),
111 is always the first database, so use
116 cannot be used in conjunction with the
120 .BI \-o " option[=value]"
125 Possible generic options/values are:
128 syslog=<subsystems> (see `\-s' in slapd(8))
129 syslog-level=<level> (see `\-S' in slapd(8))
130 syslog-user=<user> (see `\-l' in slapd(8))
134 .BI \-s " subtree-dn"
135 Only check entries in the subtree specified by this DN.
136 Implies `-b subtree-dn' if no
145 For some backend types, your
147 should not be running (at least, not in read-write
148 mode) when you do this to ensure consistency of the database. It is
158 To check the schema compliance of your SLAPD database after modifications
159 to the schema, and put any error in a file called
165 SBINDIR/slapcat -l errors.ldif
173 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)