ldapschema.1 (2010 09)
l
ldapschema(1) ldapschema(1)
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.]
----------------------------------------------------------------------
ATTRIB_MISMATCH:
definition of attribute type "<attribute name>" is incompatible with the definition
already installed in the LDAP server schema.
[The
ATTRIB_MISMATCH
message indicates the attribute type is already installed on the LDAP direc-
tory server, however, its definition does not match the LDAP server schema definition of the attribute
type with the same numeric oid or name. The mismatch can be caused by any differences in the attribute
type definition. For example, if an attribute type ’sampleAttributeB’ installed on the LDAP directory
server is multi-valued, but the definition of ’sampleAttributeB’ in the <schema> file specifies the
<singleValued/> tag, the two attribute types are mismatching. HP does not recommend installing a
schema 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.]
----------------------------------------------------------------------
Object Class Status Messages
OBJECT_INVALID:
object class definition is missing a numericoid. Edit the schema definition file to
specify one <oid> tag and its value for every <objectClassDefinition> definition.
[This message indicates the
<oid> tag and its value need to be specified in the
<objectClassDefin-
ition> 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 <objectClassDefinition> definition.
[This message indicates the
<name> tag and its value need to be specified in the
<objectClassDe-
finition>
definition in the <schema> file.]
----------------------------------------------------------------------
OBJECT_INVALID:
object class "<object name>" has an invalid numericoid. Edit the schema definition
file to specify an RFC 2252 compliant <oid> value for this object class. Valid
numericoid must consist of digits (0-9) that can be separated by a period (.). Lead-
ing zeroes are not allowed. See RFC 2252 for details.
[This message indicates the
<oid> tag value needs to be corrected in the <objectClassDefini-
tion> definition in the <schema> file. The <oid> value must be compliant with RFC 2252. See RFC
2252 for details.]
----------------------------------------------------------------------
OBJECT_INVALID:
object class "<object name>" has an invalid name. Edit the schema definition file to
specify an RFC 2252 compliant <name> value for this object class. Valid name
characters include letters (A-z), digits (0-9), semicolons (;) and dashes (-). Valid
name must begin with an alphabet letter (A-z). See RFC 2252 for details.
[This message indicates the
<name> tag value needs to be corrected in the <objectClassDefini-
tion> definition in the <schema> file. The object class name value must be compliant with RFC 2252.
HP-UX 11i v3: June 2010 Web Release − 17 − Hewlett-Packard Company 17