LDAP-UX Client Services B.05.00 Administrator's Guide

Edit the <schema> file to correct the name of the super-class in the
object class definition. The super-class used in the object class
definition must be defined either in the LDAP directory server schema
or in the <schema> file before this object class can be installed.]
OBJECT_UNRESOLVED Mandatory attribute used in the <object name> object class
definition is not defined in any LDAP server schema.
[This message indicates the mandatory attribute type specified with
the <must> tag in the given object class definition is undefined. Edit
the <schema> file to correct the name of the mandatory attribute in
the object class definition. The mandatory attribute used in the object
class definition must be defined either in the LDAP directory server
schema or in the <schema> file before this object class can be installed.]
OBJECT_UNRESOLVED Optional attribute used in “<object name>” object class definition
is not defined in any LDAP server schema.
[This message indicates the mandatory attribute type specified with
the <may> tag in the given object class definition is undefined. Edit
the <schema> file to correct the name of the optional attribute in the
object class definition. The optional attribute used in the object class
definition must be defined either in the LDAP directory server schema
or in the <schema> file before this object class can be installed.]
OBJECT_FOUND Object class “<object name>” is already installed in the LDAP
server schema.
[This message indicates the LDAP directory server schema already
includes a definition of an object class definition with the same
numeric oid or name. If the ldapschema utility is executed in the
extend mode, the given object class will not be added to the LDAP
directory server schema. This message is displayed in verbose mode
only.]
OBJECT _MISMATCH Definition of object class “<object name>” is incompatible with
the definition already installed in the LDAP server schema.
OBJECT_REJECTED Object class “<object name>” will not be added to the LDAP server
schema because it is already part of the LDAP schema.
[This message indicates the LDAP directory server schema already
includes a definition of an object class definition with the same
numeric oid or name.]
OBJECT_REJECTED Object class “<object name>” will not be added to the LDAP server
schema because its definition is invalid.
[This message indicates definition of the specified object class is
invalid. If the ldapschema utility is executed in the extend mode, the
given object class will not be added to the LDAP directory server
schema. Check the messages containing OBJECT_INVALID for
details.]
7.5.8.4 Matching rules status messages
RULE_INVALID
Matching rule is missing a numeric oid. Edit the schema definition file to
specify one <oid> tag and its value for every <matchingRuleDefiniton>
definition.
[This message indicates the <oid> tag and its value need to be specified in
the <matchingRuleDefinition> definition in the /etc/opt/ldapux/
7.5 Schema extension utility 323