1 .TH SLAPSCHEMA 8C "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2013 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slapschema \- SLAPD in-database schema checking utility
16 .BI \-d debug-level\fR]
18 .BI \-f slapd.conf\fR]
26 .BI \-l error-file\fR]
30 .BI \-o option\fR[ = value\fR]]
32 .BI \-s subtree-dn\fR]
39 is used to check schema compliance of the contents of a
42 It opens the given database determined by the database number or
43 suffix and checks the compliance of its contents with the corresponding
44 schema. Errors are written to standard output or the specified file.
45 Databases configured as
47 of this one are also output, unless \fB\-g\fP is specified.
49 Administrators may need to modify existing schema items, including
50 adding new required attributes to objectClasses,
51 removing existing required or allowed attributes from objectClasses,
52 entirely removing objectClasses,
53 or any other change that may result in making perfectly valid entries
54 no longer compliant with the modified schema.
57 tool after modifying the schema can point out
58 inconsistencies that would otherwise surface only when
59 inconsistent entries need to be modified.
62 The entry records are checked in database order, not superior first
63 order. The entry records will be checked considering all
64 (user and operational) attributes stored in the database.
65 Dynamically generated attributes (such as subschemaSubentry)
66 will not be considered.
70 Only check entries matching the asserted filter.
74 "(!(entryDN:dnSubtreeMatch:=ou=People,dc=example,dc=com))"
76 will check all but the "ou=People,dc=example,dc=com" subtree
77 of the "dc=example,dc=com" database.
78 Deprecated; use \fB-H\fP \fIldap:///???(filter)\fP instead.
81 Use the specified \fIsuffix\fR to determine which database to
82 check. The \fB\-b\fP cannot be used in conjunction
88 Enable continue (ignore errors) mode.
91 Enable debugging messages as defined by the specified
98 Specify an alternative
103 specify a config directory.
108 are specified, the config file will be read and converted to
109 config directory format and written to the specified directory.
110 If neither option is specified, an attempt to read the
111 default config directory will be made before trying to use the default
112 config file. If a valid config directory exists then the
113 default config file is ignored.
116 disable subordinate gluing. Only the specified database will be
117 processed, and not its glued subordinates (if any).
120 use dn, scope and filter from URI to only handle matching entries.
123 Write errors to specified file instead of standard output.
126 Check the \fIdbnum\fR\-th database listed in the
127 configuration file. The config database
128 .BR slapd\-config (5),
129 is always the first database, so use
134 cannot be used in conjunction with the
138 .BI \-o \ option\fR[ = value\fR]
143 Possible generic options/values are:
146 syslog=<subsystems> (see `\-s' in slapd(8))
147 syslog\-level=<level> (see `\-S' in slapd(8))
148 syslog\-user=<user> (see `\-l' in slapd(8))
153 Only check entries in the subtree specified by this DN.
154 Implies \fB\-b\fP \fIsubtree-dn\fP if no
159 Deprecated; use \fB-H\fP \fIldap:///subtree-dn\fP instead.
164 For some backend types, your
166 should not be running (at least, not in read-write
167 mode) when you do this to ensure consistency of the database. It is
177 To check the schema compliance of your SLAPD database after modifications
178 to the schema, and put any error in a file called
184 SBINDIR/slapcat \-l errors.ldif
192 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)