Regarding Entry Creation
We have DS5.2 running on AIX5.3 and we have the uid uniqueness plugin activated .
our DN for an entry in the DS is of the follwing formant: cn=Anand katuri+uid=t1h43w,ou=people,o=organization.com,c=us.
Today when i searched for an uid in the DS (o123th--ex) I got two entries with this uid...The DN's of the two entries are as follows:
1st entry:
cn=thomat rober+uid=o123th,ou=people,o=organization.com,c=us.
2nd entry
nsuniqueid= xyzzzzkja01929304+cn=thomat rober+uid=o123th,ou=people,o=organization.com,c=us
When i read the both entries, I found out that the 1st entry was created at (6:14pm0 and the second entry was created at 6:17pm. BOth the entries have same details except that the 1st entry has an value defined for an extra user -defined attribute "pwdLastModifieddate"(cutom atttribute)..
When i found more about thes with my collegeus(as am new tothis environment)..i was told that the DS itself created the second entry( witht the nsunqueid entry attribute added as an naming attirbute) when they try to add an entry to the DS...
Does this happens in DS?If so then what is the scenario that this kind of action takes place?/
# 1
> We have DS5.2 running on AIX5.3 and we have the uid
> uniqueness plugin activated .
> our DN for an
> entry in the DS is of the follwing formant: cn=Anand
> katuri+uid=t1h43w,ou=people,o=organization.com,c=us.
>
> Today when i searched for an
> uid in the DS (o123th--ex) I got two entries with
> this uid...The DN's of the two entries are as
> follows:
>
> 1st entry:
> cn=thomat
> rober+uid=o123th,ou=people,o=organization.com,c=us.
>
> 2nd entry
> nsuniqueid= xyzzzzkja01929304+cn=thomat
> rober+uid=o123th,ou=people,o=organization.com,c=us
>
> When i read the both
> entries, I found out that the 1st entry was created
> at (6:14pm0 and the second entry was created at
> 6:17pm. BOth the entries have same details except
> that the 1st entry has an value defined for an extra
> user -defined attribute "pwdLastModifieddate"(cutom
> atttribute)..
>
> When i found more about
> thes with my collegeus(as am new tothis
> environment)..i was told that the DS itself created
> the second entry( witht the nsunqueid entry attribute
> added as an naming attirbute) when they try to add an
> entry to the DS...
>
> Does this happens in DS?If so then
> what is the scenario that this kind of action takes
> place?/
Yes, this may happen in a MMR toplogy. Entries with identical DNs may be created on separate masters if they are created before the servers replicate the changes to each other. Upon replication, the replication conflict resolution mechanism will automatically rename the second entry created. An entry with a DN naming conflict is renamed by including its unique identifier, given by the operational attribute nsuniqueid, in its DN - even on a completely unsupported platform like AIX 5.3.