Duplicate CIs are getting created after the Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2020 09:51 AM
Hi Team,
I am facing an issue with the Discovery Process. For the IBM WebSphere class, duplicates are getting created after the Discovery. I have an Identification rule with the attributes Name, Class, and Node. There are few records which were created last year for them duplicates are getting created. If I run the discovery by keeping existed records then duplicates are getting created. But, If run the discovery after deleting the existed records is not creating duplicates and updating the same new record when the discovery runs again. Please help me with this.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2020 10:06 AM
Hi there,
The duplicates on the CMDB Dashboard are derived from CIs that are tagged with the discovery source field of duplicate. When this happens, a de-duplication task record is created listing or grouping all the duplicate CIs.
A CI is tagged as a duplicate either during ServiceNow discovery. During the identification phase, the IRE (hardware rule) is used to identify if the CI exists or does not exist in the CMDB to determine if an update or insert should occur. If multiple CIs exist in the CMDB as identified by the Hardware rule, then the oldest CI (in terms of creation date) is updated and its discovery source is defined as ServiceNow, however the other duplicate CI is not updated and its discovery source is flagged as duplicate. As a result of this process, a de-duplication task is created and the two CIs will display on the CMDB Dashboard under the Correctness Scorecard only after the Correctness scheduled job is run.
A second scenario exists if a duplicates exist in the CMDB and CIs do not have any discovery source defined. In this case, after the Correctness schedule job is run, these CIs will be added automatically to a de-duplication task record and also automatically be part of the calculation on the Correctness Scorecard.
for more reference PFB link,
https://www.softwebsolutions.com/resources/servicenow-cmdb-duplicates.html
Please mark correct and helpful if my answer is worth to you.
regards,
Ganesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2020 10:53 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2020 10:17 AM
HI,
Ohk so you have attributes in your identifier. Can you check if the old CI have the values in them or else it will create new CI.
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-28-2020 10:51 AM