- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-24-2023 07:23 AM
In the 'cmdb_ci_computer' table, I've identified around 150 duplicate CIs based on serial numbers. However, when I cross-checked these CIs in all asset tables, most of the serial numbers do not have duplicates in ALM.
ALM only shows one record with serial number which are shown as duplicate in cmdb but the same serial number has two records in the 'cmdb_ci_computer' table.
Upon further investigation, I discovered that the duplicate record in the 'cmdb_ci_computer' table is linked to a different serial number in the asset table. However, the configuration item attached to it is the same record that exists as a duplicate in the 'cmdb.'
I'm puzzled as to why the ALM asset serial number didn't update the CMDB CI serial number, and how the configuration item ended up with a different serial number than the CI attached to it.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-02-2023 05:22 AM
It's possible that there was some data synchronization issue between the 'cmdb_ci_computer' table and the ALM asset table, which caused discrepancies in the serial numbers. It's also possible that there was a manual error or misconfiguration during data entry or import.
It's important to ensure that all data in both systems is accurate and up-to-date, as inconsistencies can lead to inaccurate reporting and decision-making. I am afraid you may need to manually update records in one system based on data from the other system to ensure consistency.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-25-2023 04:50 AM
Are you saying you have same asset record linked to different CIs (with duplicate serial numbers)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-02-2023 05:22 AM
It's possible that there was some data synchronization issue between the 'cmdb_ci_computer' table and the ALM asset table, which caused discrepancies in the serial numbers. It's also possible that there was a manual error or misconfiguration during data entry or import.
It's important to ensure that all data in both systems is accurate and up-to-date, as inconsistencies can lead to inaccurate reporting and decision-making. I am afraid you may need to manually update records in one system based on data from the other system to ensure consistency.