• State Verified Answer
  • Replies replies
    4
  • Subscribers subscribers
    17
  • Views views
    332
  • Users 0 members are here
  • Locked Locked
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

attributes differ between servers

Nicolai Glahn
 

Hi,

From time to time, we see objects, where typically multivalue attributes are not consistent between the servers in the replica ring. For example as shown on the pictures below

One Server

The other servers

We know, that the correct value are one the first server.

The replicas shows no problems with synchronization as such, all are up to date, time is in sync etc.

No objects seems to be broken as such (ndsrepair -R)

In this instance, the object with the correct values is in one partition, and the referenced object(s) (as seen, they are DN values), are on another partition.

We supect than more than one object has those inconsistencies.

The question is, how do we make sure that all objects on server one (which we see as the authoritative truth now), are replicated in full to the other servers.

Sending an object to all replicas from iMonitor does not make the object consistent accross the replicas.

From dsrepair, "Synchronize the replica on all servers" does not make any difference either.

We could of course remove the partition from the other servers, and add them again, but that seems like a rather harsh decision.

How do we make replicas consistent?

  • 0  

    Hi,

    Check sync: ndstrace -E (all servers)

    Then check the replica state using iMonitor on all the servers, then if replication is fine, then maybe try to timestamp the attribute on the server where it is correct (enable advanced options).

    Also look at ndstrace +time +tags +sync +sydl (also all servers) to see if there is a sync problem.

  • 0   in reply to   

    ndstrace reported no errors whatsover.

    When you say "timestamp the attribute" and "enable advanced options" where do we do that?

    I could imagine that we had more than one object with inconsistent attributes. So this time I merged the partition with its parent, and of course that fixed the issue. I just have the feeling, that we could do something less cumbersome.

  • Verified Answer

    +1   in reply to   

    Hi NJensen,

    I suppose you need to activate advanced options in iMonitor:

    Click here...

    ... then select "Enabled"...

    With Advanced Mode enabled, you should then be able to see the following when an object is selected...

    ...

    As always, be aware of the potential risks shown in the warning messages.

    Best regards,
    Philipp

  • 0   in reply to   

    Thanks

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.