ODSEE 11.1.1.3.0 - A MODRDN resurrects old values (Doc ID 1340372.1)

Last updated on OCTOBER 23, 2016

Applies to:

Oracle Directory Server Enterprise Edition - Version 6.3 to 11.1.1.3.0 [Release 6.0 to 11gR1]
Information in this document applies to any platform.
***Checked for relevance on 22-Jan-2014***

Symptoms

A MODRDN results is an old RDN value reappearing within an entry, why?

The following example shows changing the rdn from 590 to 591 and then deleting the old rdn.

dn: obSeqNo=590,app=PS,o=Oblix,dc=example,dc=com
changetype: modrdn
newrdn: obSeqNo=591
deleteoldrdn: 1

The MODRDN completes without issue but a search on Master 2 shows a second value for  'obSeqNo: 576'. This value was not present prior to the MODRDN.


dn: obSeqNo=591,app=PS,o=Oblix,dc=example,dc=com
objectClass: top
objectClass: oblixGSN
obver: 10.1.4.0
obSeqNo: 576 <=========== HERE
obSeqNo: 591


Where did 576 come from?

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms