Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.
Novell Directory Services 8
Novell eDirectory 8.5 (85.xx)
Novell eDirectory 8.6 for All Platforms
Novell eDirectory 8.7 for NetWare 6
Novell NetWare 5.1
Novell NetWare 6.0
Objects sync continuously since introducing eDirectory 8.5, 8.6, 8.7
All processed = Yes, yet objects continue to sync over and over
-151 errors in trace
Introduced eDirectory 8.6 or 8.5
Transitive Vector values are missing on the transitive vector attribute
To determine if you do have a missing value on the Transitive Vector attribute, do the following:
Find the objects that are continuously syncing.
Use the following SET commands:
Capture a few sync cycles then SET TTF=OFF
Verify that objects are syncing over and over.
Use Dsbrowse to determine which replica numbers are missing from the transitive vector attribute by doing the following for each partition that has objects syncing over and over:
Load DSBROWSE | Partition Browse | Highlight the partition root object | F3 | View Attributes | Transitive Vector | Choose the Transitive Vector entry for the server you have DSBROWSE loaded on. | View Value Details | Press <Enter> to decode the attribute data | Press <ENTER> to display timestamps.
The Screen should look like this:
Replica 00001: 10-29-2001 4:49:08 pm, Event 00001
Replica 00002: 10-29-2001 5:19:09 pm, Event 00002
Replica 00003: 10-30-2001 3:23:01 am, Event 00001
Replica 00010: 10-26-2001 12:15:44 pm, Event 00005
Make note of the Replica numbers. In this case, the replica numbers are 1, 2, 3 and 10. (NOTE: These are HEX values) Next go through each of the objects syncing over and over. Highlight the object in question in DSBROWSE | Press F3 | View Object Details | Look at Creation/Modification Time:
The screen should look like this:
Creation Time: Thursday, October 11, 2001 12:15:25 pm,  
Modification Time: Monday, October 29, 2001 4:38:34 pm,  
The first set of numbers in the first bracket is the replica number. Make note of the Replica numbers. In this case the object was created by Replica number 4 and modified by Replica number 2. For every creation and modification timestamp for any object in DS, the replica number should exist as an entry in the Transitive Vector table. Because Replica number 4 created the object, there should be an entry for Replica number 4 above on the Transitive Vector attribute.
In the example above, Replica 4 is missing. It is also necessary to look at modification time on attributes of the object to determine if there are any other Transitive Vector attributes missing for those attributes.
To do this, highlight the object in question in DSBROWSE | Press F3 | View Attributes | Press enter on each attribute | View Value details | then look at modification time.
You would see the following:
Modification Time: Friday, October 12, 2001 6:22:14 pm,  
In this case, the object was modified by Replica number 2 If you find a replica number that is not referenced in the Transitive Vector attribute, this will cause the objects to sync over and over.
If you are running eDirectory 8.5 (DS.NLM 85.xx) you can apply edir8530.EXE from support.novell.com/filefinder or greater.
Load DSREPAIR (85.14 and higher) on the master of the partition | Advanced options menu | Repair local DS database | F10 to start the repair. Running the repair will add back missing Transitive Vector entries and stop the continuous syncing of objects.
If you are running NetWare 6, apply NetWare 6 Support Pack 3 or EDIR862SP3.EXE from https://support.novell.com/filefinder on all NetWare 6 servers. This will dynamically add the transitive vectors back for these objects during normal synchronization. You do not have to run a special dsrepair.
If you are running eDirectory 8.7, you will need a new DSREPAIR-ANT from EDIR8704.EXE (Version 10410.92 -or greater) on all the servers in the replica ring at the same time.
If you are running NDS 8.x or if the above solutions don't fix the problem, as a last resort, you can Repair Timestamps and Declare a new Epoch. This will essentially take all objects for a give partition and replace the modification time stamps with the current time and will also change the replica number for each time stamp to match the replica number of the master replica. For more information on the implications of using this option and on how to run it, see Implications of running "Repair Timestamps and Declare a new epoch .
NOTE: With the new DSREPAIR you will need to run a DSREPAIR -ANT. If you run a normal DSREPAIR, the transitive vectors will NOT be checked.