LDAP-UX Client Services B.04.15 with Microsoft Windows Active Directory Server Administrator's Guide (edition 8)

SCHEMA_EXISTS
No changes to the LDAP server schema are needed. All attribute types
and object classes defined in the <schema> file are already part of the
LDAP directory server schema.
[The SCHEMA_EXISTS message indicates the schema specified in the
<schema> file is already installed on the LDAP directory server. All
attribute types and object classes defined in the <schema> file are already
part 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. Check the messages containing
ATTRIB_FOUND and OBJECT_FOUND described below for details.
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/or object classes. Review the messages above and correct any
errors in the schema definition file.
[The SCHEMA_INVALID message indicates some of the attribute types
and/or 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. Review
the “Defining Attribute Types” and “Defining Object Classes” sections
for details. Also, check the messages containing ATTRIB_INVALID,
ATTRIB_UNRESOLVED, OBJECT_INVALID and
OBJECT_UNRESOLVED described below for details.
Any invalid elements and any elements that depend on them will be
excluded from being extended on the LDAP server. For example, if an
attribute type 'sampleAttributeA' 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 (i.e.,
mismatching) definitions. Review the messages above 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.
Schema Extension Utility 249