LDAP-UX Client Services B.04.10 with Microsoft Windows Active Directory Server Administrator's Guide

file. The <oid> value must be compliant with RFC 2252. See RFC 2252
for details.
ATTRIB_INVALID Attribute type “<attribute name>” has an invalid name. Edit the
schema definition file to specify an RFC 2252 compliant <name >
value for this attribute type. 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 and its value need to be
corrected in the <attributeTypeDefiniton> definition in the
<schema> file. The attribute type name value must be compliant with
RFC 2252. See RFC 2252 for details.]
ATTRIB_INVALID Attribute type “<attribute name>” must have the same usage (
<usage> tag) value as its super-type. Edit the schema definition file
to correct the usage value for this attribute or its super-type.
If the attribute type specifies a supertype, both this attribute type and
its supertype must have the same <usage> tag value. This message
indicates the <usage> tag value of the specified attribute type and the
<usage> tag value of its supertype do not match. Edit the <schema>
file to correct the discrepancy.
ATTRIB_INVALID Attribute type “<attribute name>” is missing a syntax value. Edit
the schema definition file to specify a syntax (<syntax> tag) value, or
a valid super-type (<subTypeOf>) value.
Most LDAP directory servers require attribute type definitions to
specify either the syntax value or a super-type value. This message
indicates that the specified attribute type definition in the <schema>
file does not specify either of these values. Edit the <schema> file to
specify either the <syntax> tag and its value, or a <subTypeOf> tag
and its value in the specified attribute type definition.
ATTRIB_INVALID Attribute type “<attribute name>” cannot be labeled as obsolete
(<obsolete> tag) if any other attribute types or object classes depend
on it. Edit the schema definition file to remove the <obsolete> tag
from this attribute type definition in order for it to be added to the
LDAP server schema.
Obsolete attribute types cannot be added to the LDAP directory server
schema if any other attribute types or object classes depend on them.
This messages indicates the given attribute type cannot specify the
<obsolete> tag in its definition if it is used as a super-type in any other
attribute types, or if it is used as a mandatory or optional attribute
in any object classes. Edit the <schema> file to correct this discrepancy.
ATTRIB_UNRESOLVED Super-type used in "<attribute name>” attribute type definition
is not defined in any LDAP schema.
[This message indicates the super-type specified with the
<subTypeOf> tag in the given attribute type definition is undefined.
Edit the <schema> file to correct the name of the super- type in the
attribute type definition. The super-type used in the attribute type
definition must be defined either in the LDAP directory server schema
or in the <schema> file before this attribute type can be installed.]
ATTRIB_UNRESOLVED Matching Rule "<matching rule name> " used in the <attribute
name> attribute type definition cannot be mapped because "-m -"
option is specified. This matching rule is not supported on the LDAP
server.
[This message indicates the matching rule specified with the
<equality>, <ordering> or <substr> tag in the given attribute type
definition is not supported on the LDAP directory server. Option -m
Schema Extension Utility 179