How to allow IG Imports to continue with duplicates.

book

Article ID: 131964

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 data into CA Identity Governance, you might encounter duplicates which can stop the import from completing.  In these circumstances errors like the one below can be generated. This is the expected behavior.  Is there a way to continue past this error:

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 below Knowledge article for more information on this error and its resolution.

Universe connector import failing for duplicate users
 

Environment

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

Resolution

To allow the import to continue without stopping at the error, modify the Identity Governance property "import.csv.shouldFailOnDuplicateUser" from true to false. 

1. Go to Administration / Settings / Property Settings

2. Edit Property "import.csv.shouldFailOnDuplicateUser" from true to false

<Please see attached file for image>

IG Properties

Caution:
While it is possible to allow the import process continue, It might not be a good idea as you will end up have 2 duplicated IDs in the system without notification. Please consider the consequences of this action before continuing in a production environment.

Additional Information

Please also refer to the following Knowledge Article

How to identify duplicates encountered during an Identity Governance import?

Attachments

1558686298032000131964_sktwi1f5rjvs16ew4.jpeg get_app