We have the following issue using the IBM Directory Server MA using FIM 2010 R2 (Version 4.1.3479.0).
- We provision a new object, e.g., uid=jdoe,ou=users,o=contoso, into an instance of IBM Directory Server
- The object is created in IBM Directory Server as uid=jdoe,ou=users,o=contoso
- A Full Import on the IBM Directory Server MA runs and confirms the export
- Subsequent imports, sync, and exports run successfully
- <Time passes>
- A Full Import on the IBM Directory Server MA runs, and this object shows up as a staging-error (uid=jdoe,ou=Users,o=contoso)
- Subsequent imports and syncs report errors on this object (staging-error)
Note that we do not manipulate the anchor (DN) of this object once it is created in IBM Directory Server. Other attributes are synchronized, but the object is never renamed/moved. This case change does not happen with all of the objects brought in during the Full Import, but the number of instances do increase periodically. At this point, it does look like the import is changing from a lowercase "u" to an uppercase "U" but not vice versa.
I found a related TechNet article containing the following remark:
"IBM Directory Server does not guarantee that the case of a DN component will match in all instances. On a synchronization or import from IBM Directory Server, this can manifest itself as an unexpected update. For example, if you createO=TEST, and then create the user cn=MikeDan,O=TEST, this might be imported from IBM Directory Server ascn=MikeDan,O=test. Because of the case difference, FIM treats this as an update on subsequent full imports."
Unfortunately, the article does not propose a resolution.
Has anyone encountered this issue? More importantly has anyone resolved this or found an acceptable workaround?
Note that deleting the connector space is not an acceptable workaround. :)