Novell Home

Tip for Continuous Synchronization Issue

Novell Cool Solutions: Tip

Digg This - Slashdot This

Posted: 2 Nov 2001
 

For details or updates on this tip, see TID-10065699

If you've recently upgraded to eDirectory 8.5 or 8.6 and have noticed that your directory objects are unnecessarily synchronizing, here's a new Technical Information Document (TID) that could help you out.

According to the support document, the problem is Transitive Vector values are missing on the transitive vector attribute. (We're pretty sure we don't know what that means. As long as there's a fix, we're happy.)

Here's the recommended fix:

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 SET DSTRACE=+S to capture a few sync cycles. 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 to decode the attribute data | Press to display timestamps.

The Screen should look like this:

Transitive Vectors
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, [0004] [0001]
   Modification Time: Monday, October 29, 2001 4:38:34 pm, [0002] [0005]

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, [0002] [0001]

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 FDS8520C.exe or greater This is a field test file for eDirectory 8.5 (85.xx) ONLY!

Load dsrepair (85.12b 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 eDirectory 8.6 with NetWare 6, Please call Technical Support requesting the NetWare 6 NDS team.

For details or updates on this tip, see TID-10065699


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell