prevent from creating duplicate ci records

[ssr99]

Two ci having same name same port same class  but ci which is created first (suppose created in jun) whose Install Directory is empty  but in second ci (suppose created in july) Install Directory is populated and both ci's having same discovery source as ServiceNow..

Is it Possible? if Yes then what should I do to remediate ci and how to prevent it from creating duplicate ci like?

[Prateek kumar]

On which field is your coalesce set on?

It is usually serial number but check in your config and that can help you prevent duplicates going forward

[Manmohan K]

@ssr99 

Please check the identifier rules for that particular class because you must determine first if they are duplicates or not.

If you notice that the identifier fields are matching, then they are duplicate

Steps to do it - 

Go to Discovery Definition> Identifiers and search with your cmdb class

Open the Identifier record and check each identifier entry's criterion attributes. These are used to uniquely identify your cmdb record using criterion attributes. They are checked from lowest priority to highest till there is a match of current record with existing record. if there is no match that means current record is a new record

If you determine they are duplicates, you need to investigate if you are getting wrong values for criterion attributes for some reason. If values coming are not wrong, then there should be modification done to identifier rules since current identifiers are failing to uniquely identify a record

[ssr99]

Db2 instance Table identification rule

[ssr99]

ci class manager is Db2 instance and ci identifier is out of box i haven't update it it is build with name, class, port and install directory