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

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.]
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/schema/schema-ds_type.xml file, where ds_type
corresponds to the same value specified with the -T option on the command
line when executing the ldapschema utility.]
RULE_INVALID
Matching rule is missing a name. Edit the schema definition file to specify
at least one <name> tag and its value for every <matchingRuleDefiniton>
definition.
[This message indicates the <name> tag and its value need to be specified in
the <matchingRuleDefinition> definition in the
/etc/opt/ldapux/schema/schema-ds_type.xml file, where ds_type
corresponds to the same value specified with the -T option on the command
line when executing the ldapschema utility.]
RULE_INVALID
Matching rule is missing an LDAP syntax. Edit the schema definition file to
specify one <syntax> tag and its value for every
<matchingRuleDefiniton> definition.
[This message indicates the <syntax> tag and its value need to be specified
in the <matchingRuleDefinition> definition in the
/etc/opt/ldapux/schema/schema-ds_type.xml file, where ds_type
corresponds to the same value specified with the -T option on the command
line when executing the ldapschema utility.]
RULE_INVALID Matching rule “<rule name>” used in the “<attribute name>” attribute
type definition is not supported on the LDAP server. Matching rule
“<substitute rule name>” will be used instead.
[This message indicates the specified matching rule <matching rule
name> is not supported on the LDAP directory server. However, it was
254 Command, Tool, Schema Extension Utility, and Migration Script Reference