How to fix duplicate records in CMDB

[Amit39]

Hi Team,

Scenario -: I have added manually (bulk upload through transform map script) some of the servers to the respective CMDB server class (mostly Linux and Windows). After some days once the ACL and firewall got fixed on my discovery network, my discovery MID server is able to discover those target servers which got created manually earlier.

Here is the issue -: While looking into those servers list, I can see duplicate records gets created with the same Host Name.

Example: one showing created by me which added manually earlier and another one showing created by service-now which gets discovered by ServiceNow discovery. Both are having same Host Name, IP and Name information.

May I know how and where to start and fix this duplicate entry creation issue specially for Windows and Linux servers.

Also may I know how to fix this with "CI Identifier" setup in SerivceNow.

Thank you in advance.

Regards,
Amit

[Michael Fry1]

I used this Share utility: https://developer.servicenow.com/app.do#!/share/contents/5628973_duplicate_ci_merge_utility?v=1.01&t...

and it works under Kingston, even tho it doesn't say so but test in DEV site first!

This utility merges the task data under one CI and REMOVES, or deletes the duplicate CIs. That way the task data exists under 1 active CI. You can modified the columns on the UI page so you know which CI came from Discovery vs manually created.

[johnnyjava]

Also be sure to use the CMDBTransformUtil in the future to make sure that you don't create duplicates when running imports. (I say this more for others who are reading this thread)

[Praveen37]

Hi Amit

You can manipulate the identification rule, Just go to the CI identifier and add the specific field which should checks the duplication of the records.

Also there are 6 schedule jobs on CMDB dashboard enable them, By which you can track the duplication of your Records and can directly delete it if any exists.

[johnnyjava]

Very rarely have I seen any great need to adjust the Hardware CI Identifiers that come out of box.

The only use case I can recall was to add one entry for Network Interface cards that also contained Name in the event of Bonded NICs where the IP and MAC were not unique.