How to avoid Creation of Duplicate records in cmdb_ci_appl table.

[sattar3]

Hello All,

We are getting Duplicate records in cmdb_ci_appl table through Dynatrace Integration.

I have see the Identification Rule in cmdb_identifier table which is having 2 Identification Entries.

Please check the below screenshot.

Identity Entry 1: "sys_class_name,cl_port" having 2 Parameters.

Identity Entry 2: "Running process command, Running process key parameters, sys_class_name"

Is there anything wrongly configured in the above Identifiers? Is this also a cause for creating duplicate records in cmdb_ci_appl table? How we can avoid the duplicate records creation?

If Both Identifier Entries having "sys_class_name" is an issue?

Please help me on this, so that we can avoid the duplicate record creation with same Name in cmdb_ci_appl table.

@Ankur Bawiskar @Maik Skoddow @Mark Roethof @Community Alums @Dr Atul G- LNG  @Ravi Gaurav 

Thanks in Advance,

Sattar

[Dr Atul G- LNG]

@AJ-TechTrek need your expertise here.

[AJ-TechTrek]

Hi @sattar3 ,

No need to put the Sys_class in identifier Rule, Also that Application data populated from Dynatrace, Please review and Analysis the Data first and try to understand what is unique value receiving from Dynatrace which help to understand the Unique CI for Application.

Its all game about the Identification rules only, Please check them throughly and correct them.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

Ajay Kumar

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

ServiceNow Community Rising Star 2024

[HS4]

Hi @sattar3 ,

You are getting duplicate entries, It means your data does not satisfy any of the identification criteria.

To avoid duplicates, please review your incoming data and try to identify unique parameter(s). Create/modify your rules accordingly to uniquely identify existing records.

You can have common identifier attribute across your ID rules, it's not a problem, as long as all the rules have the right set of attributes to uniquely identify a record.

If my answer helped you in any way, please then mark it as helpful or correct.

Thanks,

[Pawel_85]

Hi @sattar3 

I'm experiencing the same problem, were you able to find a solution?

Thanks in advance,