LDAP-UX Client Services B.05.01 Administrator Guide for HP directory servers and Windows ADS

of the schema on the LDAP directory server. Only attribute types and
object classes with new and unique numeric oids and names can be
added to the LDAP server schema. For more information, see the messages
containing ATTRIB_FOUND (Section 9.5.8.2 (page 377)) and
OBJECT_FOUND (Section 9.5.8.3 (page 380)). Since the definitions
specified in the <schema> file are already installed in the LDAP server
schema, the ldapschema utility will make no changes to the LDAP
directory server schema.]
SCHEMA_OK All attribute types and object classes specified in the <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.]
SCHEMA_INVALID The <schema> file contains one or more invalid definition of attribute
types and object classes. Review the messages described previously and
correct any errors in the schema definition file.
[The SCHEMA_INVALID message indicates some of the attribute types
and object classes specified in the <schema> file have invalid definitions.
This condition occurs if the definition does not conform to the LDAP
directory server schema policies or the DTD template. For more information
about defining attribute types and object classes, see Section 9.5.4.2
(page 366) and Section 9.5.4.4 (page 368). Also, for more information,
see the descriptions of the ATTRIB_INVALID, ATTRIB_UNRESOLVED,
OBJECT_INVALID and OBJECT_UNRESOLVED messages, described in
sections to follow.
Any invalid elements and any elements that depend on them will be
excluded from being extended on the LDAP server. For example, if the
sampleAttributeA attribute type has an invalid <usage> value, and
an object class sampleObjectO includes sampleAttributeA as a
mandatory or an optional attribute, neither sampleAttributeA nor
sampleObjectO can be added to the LDAP server schema until the
<usage> value is corrected. Running the ldapschema utility in verbose
mode (the -v option) can provide additional information about invalid
attribute type and object class definitions. HP recommends correcting any
invalid definitions before extending the LDAP directory server schema
with any remaining new valid definitions.]
SCHEMA_MISMATCH The <schema> file contains one or more attribute types or object classes
already installed in the LDAP server schema with incompatible
(mismatching) definitions. Review the messages described previously and
verify definitions of any mismatching schema elements. Any remaining
schema elements defined in the <schema> file cannot be added to the
LDAP server schema unless the force flag (-F option) is specified.
[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.
376 Command and tool reference