This content has been marked as final. Show 6 replies
Sounds like expected behavior if the referential integrity plugin is turned on.
Hi Chris_c, thanks for your reply.
Referential integrity is configured. For me the expected behaviour is that the DN attribute gets updated, not that the value gets deleted.
Why do you say this is expected behaviour?
I guess we might need ENG to weigh in on this, but historically the DN has always been the "identity" of the entry. When you "change" the DN of the entry, this is logically equivalent to deleting it (and then adding another, different, entry with some of the same attributes).
You might want to open a ticket with Oracle to verify. They might entertain some enhancement to the refint plugin that would preserve the identity of an entry under MODDN and use something else (like nsUniqueID) to fix references.
Note that in our DEV environment, where we only have one replica, the DN link attributes ARE updated
Only in the other environment where we have 4 replica's, the DN link attribute is deleted.
That's interesting. Is the refint plugin configured the same on all replicas? Maybe you can paste in the config.
Found the problem.
The ODS service did not have enough rights to create the "refint" file in the installation/log directory.
See http://docs.oracle.com/cd/E20295_01/html/821-1220/fsush.html for more information on refint.