How to identify duplicates encountered during an Identity Governance import?

book

Article ID: 131962

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal

Issue/Introduction

The import process transfers user information into CA Identity Governance from the native systems on which it resides.

Please refer to the CA Identity Governance Product Documentation for More information.

https://docops.ca.com/ca-identity-governance/14-1/EN/client-tools/import-and-export

When importing Active Directory Endpoints into CA Identiy Goernance via the CA Identity Manager Connector, the import can fail with the error below:

Cannot insert duplicate key in object 'dbo.Users'. The duplicate key value is (610, auser).; nested exception is java.sql.BatchUpdateException: Violation of UNIQUE KEY constraint 'IX_Users'. Cannot insert duplicate key in object 'dbo.Users'. The duplicate key value is (610, auser). 
16:23:28,528 ERROR [stderr] (import-connector thread-9) at com.eurekify.command.AbstractCommand.execute(AbstractCommand.java:54) 

See the following Knowledge Article for more information on this error and resolution.

Universe connector import failing for duplicate users
 

Environment

CA Product = IDENTITY MGMT AND GOVRNCE
Product Release =14.1 CP3
 

Resolution

Checking the configuration files with time stamp created during import from the client tool and manually reviewing the content is the only way to identify the cause of the duplicate.
 

Additional Information

Please also refer to the following Knowledge article

How to allow IG Imports to continue with duplicates.