Resolution for 'DB Read failed: No such object' When Deleting Account - CA Identity Manager

Products

• CA Identity Manager
• CA Identity Suite

Issue/Introduction

When attempting to remove an account from a global user in Identity Manager, you may encounter the error 'DB Read failed: No such object.'

This occurs because a correlation record (inclusion) remains in the Provisioning Directory, even though the endpoint account no longer exists.

Environment

Identity Manager 14.x

Cause

The 'DB Read failed: No such object' error indicates that the Identity Manager Provisioning Directory contains a stale correlation record (Inclusion) between the Global User and an endpoint account that has already been deleted from the endpoint itself.

Resolution

To resolve this, you must manually delete the stale correlation record (eTInclusionID) using an LDAP browser (such as JXplorer) or an LDAP command.

Identifying the Correlation Record

1. Locate the inclusion information at the following location: eTInclusionID=#################,etSubordinateClass=eTDYNAccount,eTSuperiorClass=eTGlobalUser,eTInclusionContainerName=Inclusions,eTNamespaceName=CommonObject,dc=im,dc=eta
2. Note that the eTInclusionID value follows the format: 'Global User's eTID @ Endpoint Account's eTID'.

Removing the Record

1. Open your preferred LDAP tool (e.g., JXplorer).
2. Connect to the Provisioning Directory.
3. Navigate to the path identified in the previous section.
4. Locate the specific eTInclusionID record.
5. Delete the correlation record to allow for the removal of the account association."

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.