LDAP-UX Client Services B.04.15 with Microsoft Windows Active Directory Server Administrator's Guide (edition 8)

Return Values From ldapschema
The ldapschema tool returns the following values:
0
The operation is successful.
–1
The operation fails.
In addition, ldapschema prints to STDOUT the overall status of the schema being queried or
extended. Based on the schema status, any combination of the following messages is displayed.
Detailed explanations of each message are specified in the square brackets following the message
body text.
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/or 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. Check the messages containing ATTRIB_FOUND and
OBJECT_FOUND described below for details.
The ldapschema utility may 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 definition of the SCHEMA_MISMATCH
message below.
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 need to 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.]
248 Command, Tool, Schema Extension Utility, and Migration Script Reference