What is the impact if we delete duplicate records from cmdb_ci_appl and cmdb_rel_ci tables

[sattar3]

Hello All,

In our system we can see in cmdb_ci_appl table having more than 25000 duplicate records.

If we delete the duplicates is there any impact in future, how should we verify?

Based on cmdb_ci_appl table names having huge number of duplicates in cmdb_rel_ci table also.

Because of these duplicates we are getting Errors in Import Sets. We are using Dynatrace Integration here.

What are the dependency tables which will impact if we delete records from cmdb_ci_appl and cmdb_rel_ci tables.

Please help me on this.

Thanks,

Sattar 

[Mark Manders]

You can possibly impact every table interacting with your CMDB. Question is: why are these duplicates? Are they created wrong and really the same, or different ones and just not unique? How do you tell if something is a duplicate? Same name? 
If you have tickets on an application, your ticket will no longer be on that application once you delete it, except if it's on the one you keep. If you have logic depending on the cmdb (routing of tickets), you can possibly block that. Where are these duplicates coming from? Are you sure deleting them today, won't get them back tomorrow? 

[sattar3]

Thanks for the reply @Mark Manders 

We are getting Errors in Transform History.

Import Set State as "Complete with Errors".

Please check this screenshot, we can see records with same name in cmdb_ci_appl table.

same in cmdb_rel_ci table contains 12 duplicates with same parent, child and type.

In cmdb_ci_appl table we can see 25000 records having duplicates, some of them having 1,24,7,11 duplicates. 

What scenarios we need to check to delete those duplicates from both the tables?

Can you please suggest what should we do in this case, everyday we can some duplicates were creating in both the tables.

Thanks,

Sattar

[Mark Manders]

Start by finding the source of the duplicates (if they are still being created). You need to stop that (check coalesce on the import set). Once you got rid of that, do a query on the task table and group by the cmdb_ci field to see if you are having duplicates used in different records. You need to correct that and then you can do a cleanup. But first: get rid of the duplicate creation.

[sattar3]

@Mark Manders , Currently there is no effect if we delete the duplicate records from cmdb_ci_appl and cmdb_rel_ci relationships, we got confirmation from Customer.

Now the thing is we need to create a IRE Rule so that no duplicates create from today onwards. The Import will run daily bases, So that we will monitor for one week and confirming this IRE Rule is working and not creating duplicates.

Could you please suggest how can i create it?

The Existing IRE on cmdb_ci_appl table, this is Out of the box.

Identifier Entries:

1.sys_class_name,cl_port

2.running_process_command,running_process_key_parameters,sys_class_name

Could you please suggest how we can handle this? 

If we create new entry in the existing with Selecting "Name in Criterion attribute", will it work? or how we can create a rule with coalesce as name, so that no duplicate records will create with same name.

Please help me on this.

@Ankur Bawiskar @Community Alums @AG - LearnNGrow  

Thanks,

Sattar