LDAP-UX Client Services B.05.01 Administrator Guide for HP directory servers and Windows ADS

9.5.8.1 Schema status messages
SCHEMA_NEW The <schema> file contains attribute types and object classes that are
not defined in the LDAP directory server schema.
[The SCHEMA_NEW message indicates all attribute types and object classes
defined in the <schema> file are new to the LDAP directory server. The
SCHEMA_NEW message indicates none of the specified definitions are
currently installed in the LDAP server schema.]
SCHEMA_FOUND Subset of attribute types and object classes defined in the <schema> file
are already part of the LDAP server schema.
[The SCHEMA_FOUND message indicates one or more attribute type or
object class definitions specified in the <schema> file are already installed
in the LDAP server schema. Such elements will be excluded from being
extended on the LDAP server. Only attribute types and object classes with
new and unique numeric oids and names can be added to the LDAP
server schema. For more information, see the messages containing
ATTRIB_FOUND (Section 9.5.8.2 (page 377)) and OBJECT_FOUND
(Section 9.5.8.3 (page 380)).
The ldapschema utility can install any remaining new elements that are
not already defined in the LDAP server schema if both of the following
two conditions are met:
• The LDAP schema defined in the <schema> file is compatible with
the LDAP server schema. The two schemas are compatible if the
definitions of any elements found in the LDAP server schema match
their definitions specified in the <schema> file.
If the SCHEMA_MISMATCH message is displayed, the two schemas
are not compatible. This means one or more elements installed on
the LDAP server have definitions different from those specified in the
<schema> file. Installation of any remaining new elements is not
recommended. See the description of the SCHEMA_MISMATCH
message, later in this section.
If the SCHEMA_MISMATCH message is not displayed, the two schemas
are compatible. The schema specified in the <schema> file partially
exists on the LDAP server schema, and can be extended with any
remaining new valid attribute type and object class definitions.
• The LDAP schema defined in the <schema> file is valid.
If the SCHEMA_INVALID message is displayed, one or more
definitions specified in the <schema> file are invalid and cannot be
added to the LDAP server schema. Such definitions must be corrected
before the new schema elements can be extended on the LDAP server.
If the SCHEMA_INVALID message is not displayed, the schema
definition in the <schema> file is valid. It partially exists on the LDAP
server schema, and can be extended with any remaining new valid
attribute type and object class definitions.]
SCHEMA_EXISTS No changes to the LDAP server schema are needed. All attribute types
and object classes defined in the <schema> file are already part of the
LDAP directory server schema.
[The SCHEMA_EXISTS message indicates the schema specified in the
<schema> file is already installed on the LDAP directory server. All attribute
types and object classes defined in the <schema> file are already part
9.5 Schema extension utility 375