ldapschema.1 (2010 09)

l
ldapschema(1) ldapschema(1)
OBJECT_UNRESOLVED:
mandatory attribute used in "<object name>" object class definition is not defined in
any LDAP schema.
[This message indicates the mandatory attribute type specified with the
<must> tag in the given object
class definition is undefined. Edit the <schema> file to correct the name of the mandatory attribute in the
object class definition. The mandatory attribute 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.]
----------------------------------------------------------------------
OBJECT_UNRESOLVED:
optional attribute used in "<object name>" object class definition is not defined in
any LDAP schema.
[This message indicates the optional attribute type specified with the
<may> tag in the given object class
definition is undefined. Edit the <schema> file to correct the name of the optional attribute in the object
class definition. The optional attribute 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.]
----------------------------------------------------------------------
OBJECT_FOUND:
object class "<object name>" is already installed in the LDAP server schema.
[This message indicates the LDAP directory server schema already includes a definition of an object class
definition with the same numeric oid or name. If the
ldapschema utility is executed in the extend
mode, the given object class will not be added to the LDAP directory server schema. This message is
displayed in verbose mode only. Also, the following message will appear:]
----------------------------------------------------------------------
OBJECT_REJECTED:
object class "<object name>" will not be 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 object class
definition with the same numeric oid or name.]
----------------------------------------------------------------------
OBJECT_REJECTED:
object class "<object name>" will not be added to the LDAP server schema because
its definition is invalid.
[This message indicates definition of the specified object class is invalid. If the
ldapschema utility is
executed in the extend mode, the given object class will not be added to the LDAP directory server
schema. Check the messages containing
OBJECT_INVALID
for details.]
----------------------------------------------------------------------
OBJECT_MISMATCH:
definition of object class "<object name>" is incompatible with the definition already
installed in the LDAP server schema.
[The
OBJECT_MISMATCH message indicates the object class is already installed on the LDAP directory
server, however, its definition does not match the LDAP server schema definition of the object class with
the same numeric oid or name. The mismatch can be caused by any differences in the object class
definition. For example, if an object class sampleObjectB’ installed on the LDAP directory server has two
optional attributes ( ’sampleAttributeA and ’sampleAttributeB’ ), but the definition of ’sampleObjectB’ in
the <schema> file specifies three optional attributes ( ’sampleAttributeA , sampleAttributeB’ and ’sam-
pleAttributeC’ the two attribute types are mismatching. HP does not recommend installing a schema con-
taining 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 any-
way, use the force flag (the
-F option) to add them to the LDAP server schema.]
----------------------------------------------------------------------
Matching Rule Status Messages
RULE_INVALID: matching rule is missing a numericoid. Edit the schema definition file to specify
one <oid> tag and its value for every <matchingRuleDefinition> definition.
HP-UX 11i v3: June 2010 Web Release 19 Hewlett-Packard Company 19