Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

CMDB CI Missing Due to Multiple Serial Number and Source Records Updating the Same CI

Kent Gloriana
Tera Contributor

Hi Everyone,

I'm currently investigating an issue in our ServiceNow CMDB where some expected CIs are missing.

After reviewing the data, I found that multiple entries in the CMDB Serial Number table (cmdb_serial_number) and multiple records in the Source table (sys_object_source) appear to be associated with and updating the same CI. As a result, different devices that should exist as separate CIs seem to be getting consolidated into a single CI record.

For example:

  • Device A and Device B exist as separate devices in the source system.
  • Each device has its own hostname, serial number, and source record.
  • However, in CMDB, both source records end up updating the same CI.
  • The other expected CI is never created, which results in a missing CI in the CMDB.

I would like to understand the following:

  1. What are the best practices for investigating and correcting this issue?
  2. How should incorrect records in cmdb_serial_number and sys_object_source be handled?
  3. Is it recommended to delete incorrect serial number relationships and source mappings so that the next import/discovery can create the missing CI correctly?
  4. What are the common causes of multiple source records updating a single CI?
  5. Are there any recommended approaches to prevent this from recurring, particularly when using SCCM/Import Sets/IRE?
1 REPLY 1

abbasshaik4
Tera Sage

Hello @Kent Gloriana,

 

Please refer to the link's below:
Serial Number changing on CI records, causing dupl... - ServiceNow Community

How to troubleshoot duplicate CMDB CI records - Support and Troubleshooting

 

If it is helpful, please mark it as helpful and accept the correct solution by referring to this solution in the future it will be helpful to them.

 

Thanks & Regards,

Abbas Shaik