37.6 Orphaned Objects in the Configuration Store

If you delete a User object in LDAP, the objects in the configuration datastore related to that user can become orphaned. The system uses these objects for federated identity and user profiles. Currently, there are no known issues related to orphaned identity objects, but they might affect system performance. Orphaned user profile objects might also affect user lookup operations, and therefore you should remove them.

To do so, you first delete the user’s profile before you delete a User object, as described in the following steps:

  1. In iManager or an LDAP browser, edit the attributes of the User object that you are going to delete.

  2. Note the value of the User object’s GUID attribute (for eDirectory), objectGUID attribute (for Active Directory*), or the nsuniqueid attribute (for SunOne*).

  3. On the Access Manager trust/configuration datastore, locate any containers that use the following naming patterns:

    cn=LUP*,cn=SCC*,cn=cluster,cn=nids,ou=accessManagerContainer,o=novell,cn=LibertyUserProfiles*,cn=SCC*,cn=cluster,cn=nids,ou=accessManagerContainer,o=novell.

  4. Look for a child inside of these containers that is named by using the GUID noted in Step 2. There should only be one profile object for each GUID.

  5. Delete that child profile object.

  6. Repeat these steps for each User object that you want to delete.

  7. Delete the User objects.