DSREPAIR.NLM | Advanced Options | Schema Import fails

(Last modified: 09Oct2002)

This document (10066905) is provided subject to the disclaimer at the end of this document.

fact

Novell eDirectory 8.6 for All Platforms

Novell NetWare 6.0

symptom

DSREPAIR.NLM | Advanced Options | Schema Import fails

NetWare 6 components error on configuration

Error: "603 No such attribute"

Error occurs in SET DSTRACE=+schema

cause

If there is inconsistent schema on the source server, the schema import will abort at the point of the inconsistency.  If this inconsistency is on a class object, depending how far the import went, there may be many partially added classes.  Classes are added in stages.  The first stage is to add the name with no other components (superclasses, containment, naming, attributes).  This will succeed.  Typically, the errors will be detected when populating the "forward referenced" class.  If the import aborts, many half populated schema classes are left in the tree which will cause problems with the schema's associated products (ie licensing, nmas, iManage, etc, etc, etc.)

fix

There are many documents that suggest a schema import from a stand alone NetWare 6 server to the production tree before adding the first NetWare 6 box to the tree.  If the schema import fails, the following must be done to remedy the problem:
1.  The incorrect schema must be identified.
2.  The incorrect schema must be removed from the target tree.
3.  The schema inconsistency on the source server must be fixed.
4.  Re-import the schema.

1.  The incorrect schema must be identified.
Perform a schema compare against the stand alone NetWare 6 server and the production tree.  (See NOVL68490 - Comparing Schema between two servers for more information on how to do this).  Identify difference in Containment, Naming, SuperClasses, Mandatory Attributes and Optional Attributes.  The production tree will NOT have the items mentioned above and the stand alone NetWare 6 server WILL have them.

2.  The incorrect schema must be removed from the target tree.
Use ConsoleOne Schema Manager (Highlight the tree object in the left pane, go to Tools | Schema Manager) to remove the classes that are not added correctly.

3.  The schema inconsistency on the source server must be fixed.
View the SYS:\SYSTEM\DSREPAIR.LOG.  Find the section which discusses the import.  Identify the object that is giving errors.  Look up the specific error in the knowledge base  Novell KnowledgeBase and solve the error.

4. Re-import the schema.

DSREPAIR version 85.15 or later resolves this issue.

For additional information on eDirectory 8.6, please see the following solution.   TID #10066455 - eDirectory 8.6 Readme Addendum

document

Document Title:	DSREPAIR.NLM | Advanced Options | Schema Import fails
Document ID:	10066905
Solution ID:	NOVL66404
Creation Date:	18Dec2001
Modified Date:	09Oct2002
Novell Product Class:	NetWare

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.