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

See the descriptions of the ATTRIB_MISMATCH and OBJECT_MISMATCH
messages 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 example, if a
sampleAttributeAattribute type 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
mismatching 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_REJECTED The <schema> file contains no valid attribute type or object class
definitions that can be added to the LDAP directory server schema. It
defines elements already installed in the LDAP directory server schema,
or contains invalid definitions that hence cannot be installed. Review the
messages described previously and correct any errors in the schema
definition file.
[The SCHEMA_REJECTED message indicates no attribute type or object
class definitions specified in the <schema> file meet the requirement of
being both new and valid, and, therefore, cannot be added to the LDAP
server schema. Any invalid definitions must be corrected before they can
be added to the LDAP directory server schema.
See the descriptions of the ATTRIB_INVALID, ATTRIB_UNRESOLVED,
ATTRIB_MISMATCH, OBJECT_INVALID, OBJECT_UNRESOLVED,
OBJECT_MISMATCH, SCHEMA_INVALID and SCHEMA_MISMATCH
messages in subsequent sections for information about which attribute
type and object class definitions prevent the schema from being installed.
If the <schema> file contains any mismatching or invalid definitions, HP
does not recommend installing the schema on the LDAP server.]
9.5.8.2 Attribute type status messages
ATTRIB_INVALID Attribute type definition is missing a numeric oid. Edit the schema
definition file to specify one <oid> tag and its value for every
<attributeTypeDefiniton> definition.
[This message indicates the <oid> tag and its value need to be
specified in the <attributeTypeDefiniton> definition in the
<schema> file.]
ATTRIB_INVALID Attribute type definition is missing a name. Edit the schema definition
file to specify at least one <name> tag and its value for every
<attributeTypeDefiniton> definition.
[This message indicates the <name> tag and its value need to be
specified in the <attributeTypeDefiniton> definition in the
<schema> file.]
ATTRIB_INVALID Attribute type “ <attribute name>” has an invalid numericoid. Edit the
schema definition file to specify an RFC 2252 compliant <oid> value
for this attribute type. Valid numericoid must consist of digits (0-9) that
9.5 Schema extension utility 377