1 .TH SLAPSCHEMA 8C "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2010 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]
24 .BI \-l error-file\fR]
28 .BI \-o option\fR[ = value\FR]]
30 .BI \-s subtree-dn\fR]
37 is used to check schema compliance of the contents of a
40 It opens the given database determined by the database number or
41 suffix and checks the compliance of its contents with the corresponding
42 schema. Errors are written to standard output or the specified file.
43 Databases configured as
45 of this one are also output, unless \fB\-g\fP is specified.
47 Administrators may need to modify existing schema items, including
48 adding new required attributes to objectClasses,
49 removing existing required or allowed attributes from objectClasses,
50 entirely removing objectClasses,
51 or any other change that may result in making perfectly valid entries
52 no longer compliant with the modified schema.
54 .B slapschema tool after modifying the schema can point out
55 inconsistencies that would otherwise surface only when
56 inconsistent entries need to be modified.
59 The entry records are checked in database order, not superior first
60 order. The entry records will be checked considering all
61 (user and operational) attributes stored in the database.
62 Dynamically generated attributes (such as subschemaSubentry)
63 will not be considered.
67 Only check entries matching the asserted filter.
71 "(!(entryDN:dnSubtreeMatch:=ou=People,dc=example,dc=com))"
73 will check all but the "ou=People,dc=example,dc=com" subtree
74 of the "dc=example,dc=com" database.
77 Use the specified \fIsuffix\fR to determine which database to
78 check. The \fB\-b\fP cannot be used in conjunction
84 Enable continue (ignore errors) mode.
87 Enable debugging messages as defined by the specified
94 Specify an alternative
99 specify a config directory.
104 are specified, the config file will be read and converted to
105 config directory format and written to the specified directory.
106 If neither option is specified, an attempt to read the
107 default config directory will be made before trying to use the default
108 config file. If a valid config directory exists then the
109 default config file is ignored.
112 disable subordinate gluing. Only the specified database will be
113 processed, and not its glued subordinates (if any).
116 Write errors to specified file instead of standard output.
119 Check the \fIdbnum\fR\-th database listed in the
120 configuration file. The config database
121 .BR slapd\-config (5),
122 is always the first database, so use
127 cannot be used in conjunction with the
131 .BI \-o \ option\fR[ = value\fR]
136 Possible generic options/values are:
139 syslog=<subsystems> (see `\-s' in slapd(8))
140 syslog\-level=<level> (see `\-S' in slapd(8))
141 syslog\-user=<user> (see `\-l' in slapd(8))
146 Only check entries in the subtree specified by this DN.
147 Implies \fB\-b\fP \fIsubtree-dn\fP if no
156 For some backend types, your
158 should not be running (at least, not in read-write
159 mode) when you do this to ensure consistency of the database. It is
169 To check the schema compliance of your SLAPD database after modifications
170 to the schema, and put any error in a file called
176 SBINDIR/slapcat \-l errors.ldif
184 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)