LDAP-UX Client Services B.05.00 Administrator's Guide
numeric oid or name. If the ldapschema utility is executed in the
extend mode, the given attribute type will not be added to the LDAP
directory server schema. This message is displayed in verbose mode
only.]
ATTRIB_MISMATCH Definition of attribute type “<attribute name>” is incompatible
with the definition already installed in the LDAP server schema.
ATTRIB_REJECTED attribute type “<attribute 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 attribute type definition with the same
numeric oid or name.]
ATTRIB_REJECTED attribute type “<attribute name>” will not be added to the LDAP
server schema because its definition is invalid.
[This message indicates definition of the specified attribute type is
invalid. If the ldapschema utility is executed in the extend mode,
the given attribute type will not be added to the LDAP directory
server schema. Check the messages containing ATTRIB_INVALID
for details.]
7.5.8.3 Object class status messages
OBJECT_INVALID
Object class definition is missing a numeric oid. Edit the schema
definition file to specify one <oid> tag and its value for every
<objectClassDefiniton> definition.
[This message indicates the <oid> tag and its value need to be specified
in the <objectClassDefinition> definition in the <schema> file.]
OBJECT_INVALID
Object Class definition is missing a name. Edit the schema definition
file to specify at least one <name> tag and its value for every
<ObjectClassDefiniton> definition.
[This message indicates the <name> tag and its value need to be
specified in the <objectClassDefinition> definition in the
<schema> file.]
OBJECT_INVALID Object class “<object name>” has an invalid object type value. Edit
the schema definition file to modify the value specified with the
<type> tag, which can be one of the following:
• STRUCTURAL
• AUXILIARY
• ABSTRACT
[This message indicates the <type> tag value needs to be corrected
in the<objectClassDefinition> definition in the <schema> file.
Possible object class type values are STRUCTURAL, AUXILIARY or
ABSTRACT. Any other type values are rejected. If the <type> tag is
not specified in the <objectClassDefinition> definition, the
default object class type value is STRUCTURAL. See RFC 2252 for
details.]
OBJECT_UNRESOLVED Super-class used in "<object name>” object class definition is not
defined in any LDAP schema.
[This message indicates the super-class specified with the
<subClassOf> tag in the given object class definition is undefined.
322 Command and tool reference