LDAP-UX Client Services B.05.01 Administrator Guide for HP directory servers and Windows ADS
ATTRIB_REJECTED attribute type “<attribute name>” is not 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>” is not 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 is not added to the LDAP directory server schema.
For more information, see the messages containing ATTRIB_INVALID.]
9.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. For more information,
see RFC 2252.]
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. 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.]
380 Command and tool reference