ldapschema.1 (2010 09)

l
ldapschema(1) ldapschema(1)
See RFC 2252 for details.]
----------------------------------------------------------------------
OBJECT_INVALID:
object class "<object name>" specifies 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
<objectClassDefini-
tion> 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_INVALID:
object class "<object name>" cannot be labeled as obsolete (<obsolete> tag) if any
other object classes depend on it.
[Obsolete object classes cannot be added to the LDAP directory server schema if any other object classes
depend on them. This messages indicates the given object class cannot specify the
<obsolete> tag in
its definition if it is used as a superclass in any other object classes. Edit the <schema> file to correct this
discrepancy.]
----------------------------------------------------------------------
OBJECT_INVALID:
abstract object class "<object name>" cannot have a non-abstract superclass
"<superclass object name>".
[Abstract object classes can specify only abstract superclasses. This message indicates the specified
abstract object class specifies a superclass (using a
<subClassOf> tag) that is not abstract. Edit the
<schema> file to correct this discrepancy.]
----------------------------------------------------------------------
OBJECT_INVALID:
structural object class "<object name>" cannot have an auxiliary superclass "<super-
class object name>".
[Structural object classes can specify only abstract or structural superclasses. Structural object classes
cannot specify auxiliary superclasses. This message indicates the specified structural object class
specifies a superclass (using a
<subClassOf> tag) that is auxiliary. Edit the <schema> file to correct
this discrepancy.]
----------------------------------------------------------------------
OBJECT_INVALID:
auxiliary object class "<object name>" cannot have a structural superclass "<super-
class object name>".
[Auxiliary object classes can specify only abstract or auxiliary superclasses. Auxiliary object classes can-
not specify structural superclasses. This message indicates the specified auxiliary object class specifies a
superclass (using a
<subClassOf> tag) that is structural. Edit the <schema> file to correct this
discrepancy.]
----------------------------------------------------------------------
OBJECT_UNRESOLVED:
super-class used in "<object name>" object class definition is not defined in any
LDAP schema.
[This message indicates the superclass specified with the
<subClassOf> tag in the given object class
definition is undefined. Edit the <schema> file to correct the name of the superclass in the object class
definition. The superclass 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.]
----------------------------------------------------------------------
18 Hewlett-Packard Company − 18 − HP-UX 11i v3: June 2010 Web Release