Alternate primary key not checked for SAPUser during sync (4326452)

Alternate primary key not checked for SAPUser during sync

Alternate primary key is not checked for SAPUser during sync. 

In D1IM, the field SAPUser.DistinguishedName is defined as alternate primary key. However since the target system has no unique fields, we cannot be sure the the DistinguishedName really is unique. Because of this, vi_View_AlternateNamespaceKeys does not return anything for SAPUser. As a result the consistency check does not return any issues for duplicate entries and fullsync does not throw errors.

WORKAROUND

You can monitor the jobservice log for the string "An item with the same key has already been added" or the table NamespaceSyncError for messagestring like '%already an object using this alternate key%'. Also, you should check USR01 and USR02 for dupliate entries or empty accountnames.

STATUS

This known issue cannot be fixed in D1IM.