2.3 Resolving Novell eDirectory or NDS Schema Synchronization Issues

The first step in successfully resolving eDirectory or NDS schema inconsistencies is to identify which server’s schema is incomplete. Viewing the schema can be done using the tools available for download from Novell, such as dsview.nlm which is often included as part of the ds.nlm update files.

After identifying the server with the incomplete schema, determine the course of action to take. The following are three options for resetting a server’s schema.

2.3.1 Option 1

Before performing this operation, do the following:

  1. Make sure all NetWare servers are running eDirectory or NDS v5.95 (or later).

  2. Resolve all communication errors.

Then declare a new epoch on the schema for the eDirectory or NDS tree using DSREPAIR.

2.3.2 Option 2

Using INSTALL, NWCONFIG, or DSMAINT, do the following steps:

  1. Temporarily assign any references to the server to another object.

  2. Uninstall and reinstall the server.

  3. Reassign references back to the server object.

2.3.3 Option 3

With the assistance of Novell Technical Services, clear the Synchronized Up to and Modification timestamps for the schema definitions in the affected servers’ database. This allows the affected server to receive the newer schema definitions from the other eDirectory or NDS servers.