ldapschema.1 (2010 09)

l
ldapschema(1) ldapschema(1)
[The SCHEMA_FOUND message indicates one or more attribute type or object class definitions specified in
the <schema> file are already installed in the LDAP server schema. Such elements will be excluded from
being extended on the LDAP server. Only attribute types and object classes with new and unique
numeric oids and names can be added to the LDAP server schema. Check the messages containing
ATTRIB_FOUND and OBJECT_FOUND described below for details.
The
ldapschema utility may install any remaining new elements that are not already defined in the
LDAP server schema if both of the following two conditions are met.
1. The LDAP schema defined in the <schema> file is compatible with the LDAP server schema. The two
schemas are compatible if the definitions of any elements found in the LDAP server schema match
their definitions specified in the <schema> file.
If the
SCHEMA_MISMATCH
message is displayed, the two schemas are not compatible. This means
one or more elements installed on the LDAP server have definitions different from those specified in
the <schema> file. Installation of any remaining new elements is not recommended. See definition of
the
SCHEMA_MISMATCH
message below.
If the
SCHEMA_MISMATCH
message is not displayed, the two schemas are compatible. The schema
specified in the <schema> file partially exists on the LDAP server schema, and can be extended with
any remaining new valid attribute type and object class definitions.
2. The LDAP schema defined in the <schema> file is valid.
If the
SCHEMA_INVALID message is displayed, one or more definitions specified in the <schema> file
are invalid and cannot be added to the LDAP server schema. Such definitions need to be corrected
before the new schema elements can be extended on the LDAP server.
If the
SCHEMA_INVALID message is not displayed, the schema definition in the <schema> file is
valid. It partially exists on the LDAP server schema, and can be extended with any remaining new
valid attribute type and object class definitions.]
----------------------------------------------------------------------
SCHEMA_MISMATCH:
file "<schema>" contains one or more attribute types or object classes already
installed in the LDAP server schema with incompatible (i.e. mismatching)
definitions. Review the messages above and verify definitions of any mismatching
schema elements. If any remaining valid schema elements defined in the
"<schema>" file exist, use the force flag ("-F" option) to add them to the LDAP server
schema.
[The
SCHEMA_MISMATCH
message indicates one or more attribute types or object classes defined in the
<schema> file are already installed on the LDAP directory server, however, their definitions do not
match. This means that some attribute type or object class definitions specified in the <schema> file do
not match the LDAP server schema definitions of the elements with the same numeric oids or names.
Check the messages containing
ATTRIB_MISMATCH
and OBJECT_MISMATCH described below for the
exact instances of attribute types and object classes, respectively, causing the schema mismatch.
The mismatch is caused by any differences in element definitions, such as equality matching rule, single-
valued setting, attribute syntax, object class type, attribute types an object class includes, etc. For exam-
ple, if an attribute type ’sampleAttributeA’ installed on the LDAP directory server specifies IA5 String
syntax, but the definition of ’sampleAttributeA’ in the <schema> file specifies Unicode String syntax, the
two attribute types are mismatching. HP does not recommend installing schemas containing mismatch-
ing definitions. If the <schema> file defines any new valid attribute types or object classes that are not
present in the LDAP directory server schema and you would like to install them anyway, use the force
flag (the
-F option) to add them to the LDAP server schema.]
----------------------------------------------------------------------
SCHEMA_OK: all attribute types and object classes defined in "<schema>" file are valid.
[The
SCHEMA_OK message indicates the definitions of attribute types and object classes specified in the
<schema> file have valid XML format and conform to the DTD template and the LDAP directory server
schema policies. This message also indicates no mismatching/incompatible definitions specified in the
<schema> file are installed on the LDAP server.]
----------------------------------------------------------------------
HP-UX 11i v3: June 2010 Web Release − 13 − Hewlett-Packard Company 13