ldapschema.1 (2010 09)

l
ldapschema(1) ldapschema(1)
SCHEMA_INVALID:
file "<schema>" contains one or more invalid definitions of attribute types and/or
object classes. Review the messages above and correct any errors in the schema
definition file.
[The
SCHEMA_INVALID
message indicates some of the attribute types and/or object classes specified in
the <schema> file have invalid definitions. This condition occurs if the definition does not conform to the
LDAP directory server schema policies or the DTD template. Review the Defining Attribute Types and
Defining Object Classes sections for details. Also, check the messages containing
ATTRIB_INVALID
,
ATTRIB_UNRESOLVED
, OBJECT_INVALID
and OBJECT_UNRESOLVED
described below for details.
Any invalid elements and any elements that depend on them will be excluded from being extended on the
LDAP server. For example, if an attribute type ’sampleAttributeA’ has an invalid
<usage> value, and
an object class ’sampleObjectO’ includes ’sampleAttributeA’ as a mandatory or an optional attribute, nei-
ther ’sampleAttributeA’ nor ’sampleObjectO’ can be added to the LDAP server schema until the
<usage>
value is corrected. Running the ldapschema utility in verbose mode (the
-v option) can provide addi-
tional information about invalid attribute type and object class definitions. HP recommends correcting
any invalid definitions before extending the LDAP directory server schema with any remaining new valid
definitions.]
----------------------------------------------------------------------
SCHEMA_REJECTED:
file "<schema>" contains no valid attribute type or object class definitions that can
be added to the LDAP server schema. It defines elements already installed in the
LDAP server schema, or contains invalid definitions that hence cannot be installed.
Review the messages above and correct any errors in the schema definition file.
[The
SCHEMA_REJECTED
message indicates no attribute type or object class definitions specified in the
<schema> file meet the requirement of being both new and valid, and, therefore, cannot be added to the
LDAP server schema. Any invalid definitions need to be corrected before they can be added to the LDAP
directory server schema.
Check the messages containing
ATTRIB_INVALID
, ATTRIB_UNRESOLVED, ATTRIB_MISMATCH
,
OBJECT_INVALID, OBJECT_UNRESOLVED
, OBJECT_MISMATCH, SCHEMA_INVALID
and
SCHEMA_MISMATCH for details on which attribute type and object class definitions prevent the schema
from being installed.
If the <schema> file contains any mismatching or invalid definitions, HP does not recommend installing
the schema on the LDAP server.]
----------------------------------------------------------------------
Attribute Type Status Messages
ATTRIB_INVALID:
attribute type definition is missing a numericoid. Edit the schema definition file to
specify one <oid> tag and its value for every <attributeTypeDefinition> definition.
[This message indicates the
<oid> tag and its value need to be specified in the <attributeTypeDe-
finition> definition in the <schema> file.]
----------------------------------------------------------------------
ATTRIB_INVALID:
attribute type definition is missing a name. Edit the schema definition file to
specify at least one <name> tag and its value for every <attributeTypeDefinition>
definition.
[This message indicates the
<name> tag and its value need to be specified in the <attributeTypeDe-
finition> definition in the <schema> file.]
----------------------------------------------------------------------
ATTRIB_INVALID:
attribute type "<attribute name>" specifies an unrecognized <usage> value. Sup-
ported values are: directoryOperation, distributedOperation, dSAOperation or
userApplications.
[This message indicates the
<usage> tag value needs to be corrected in the <attributeTypeDefin-
ition> definition in the <schema> file. Possible attribute type usage values are
14 Hewlett-Packard Company − 14 − HP-UX 11i v3: June 2010 Web Release