Error: -603 in DSREPAIR after running DSREPAIR -A0

  • 10067431
  • NOVL68484
  • 10-Jan-2002
  • 07-Feb-2003

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Fact

Novell NetWare 5.0

Novell NetWare 5.1

Novell NetWare 6.0

Novell Directory Services

Symptom

Error: -603 in DSREPAIR after running DSREPAIR -A0

Using TID #10065372 to fix -613 errors

DS synchronization is extremely slow

Replicas stuck in NEW states

Cause

When using the DSREPAIR -A0 switch to correct the problem with incorrect syntax on attributes "modifersName" and "creatorsName", the repair strips the two attributes out of schema on the server.  The TID mentioned above specifies that after running the switch, a Post NetWare 5 Schema update and Optional Schema Enhancements should be run from a server holding a copy of the Root Partition to make sure those attributes are added correctly back to the server.  Either this step hasn't been completed or the server with the Master hasn't sent the schema back to the problem server correctly.

Fix

Usually DSREPAIR | Report Synchronization Status will give you a good idea of which servers are having the problem.  Any servers reporting a -603 remote should be suspect.  There are two other ways to check whether the problem exists:

1) Use DSBROWSE | Schema Browse | [Schema Root] | [Attribute Definitions] | and then look in the list for either "modifiersName" and "creatorsName".  If they do not exist, or they exist but show up as [Deleted Entry], the server has NOT received these two attributes yet from the Root of the tree.

2a) If the server has a DS version earlier than 8.6, use SCHCMP.EXE to do a schema compare between the server that holds the Master of Root and the suspect server.  For more information on how to use SCHCMP.EXE, see TID #10067442 - Comparing Schema between two servers.  The server has the problem if the output from the schema compare shows something similar to the following:

Attributes unique to FS1
modifersName
creatorsName

You may see Definition differences, but these are common in mixed DS environments and are cosmetic.

Once you have determined which servers have the problem, the easiest way to correct the problem is to reset the local schema on the suspect server.  NOTE:  Before doing anything involving schema, a backup of Directory Services should be taken.  At the console prompt type DSREPAIR -RC to grab a quick backup of DS.  

To reset the local schema, LOAD DSREPAIR | Advanced Options | Global Schema Operations | Reset Local Schema.  A log screen will appear saying that the reset has been scheduled.  NOTE:  If the server you are trying to reset local schema on holds a copy of the ROOT partition, the process will abort. You cannot reset schema on a server that holds a copy of the ROOT partition.  If you have a server that has a copy of ROOT and also has the problem, remove the copy of ROOT and then try the reset once more.

Once the Reset has been scheduled, to hurry up the process, type the following at the console prompt of the server that holds the Master replica of the ROOT partition:

SET DSTRACE = +schema
SET DSTRACE = *ss

Give the synchronization some time and then go back through either DSBROWSE or SCHCMP and the modifersName and creatorsName should now show up and -603 errors should go away.

2b) If the server has DS version 8.6 or later, use NDS iMonitor to do the schema compare

 

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

For additional information on eDirectory 8.7, please see the following solution.  NOVL81742 - Novell edirectory 8.7.x Readme Addendum

For additional information on NetWare 6, please see the following solution.  TID #10064501 - NetWare 6 Readme Addendum

Feedback service temporarily unavailable. For content questions or problems, please contact Support.