My Oracle Support Banner

ODSEE - A MODRDN Results in an Old RDN Value Reappearing Within an Entry, Why? (Doc ID 1340372.1)

Last updated on FEBRUARY 27, 2019

Applies to:

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


A MODRDN results in 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: obNo=590,app=PS,dc=example,dc=com
changetype: modrdn
newrdn: obNo=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: obNo=591,app=PS,dc=example,dc=com
objectClass: top
obNo: 576 <=========== HERE
obNo: 591

Where did 576 come from?




To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.