CMDB 360 Data Mismatch Report showing outdated values although CI and source data are correct
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi Team,
I'm investigating a CMDB 360 Data Mismatch issue.
Issue Observed:
- A CI shows mismatches for attributes such as Operating System in the CMDB 360 Data Mismatch report.
- The current CI record contains the correct values.
- The authoritative source also contains the correct values.
- However, records in cmdb_multisource_data still contain older values, causing the mismatch report to show discrepancies.
- for eg: For the actual ci , source: servicenow, OS value :windows server 2012 standard
- In the mutisourec data table, for the same ci , source:SG-TaniumSN, OS value: Windows server 2012 standard but source is servicenow
Investigation Done:
- Verified the CI values are correct.
- Verified source values are correct.
- Reviewed reconciliation rules.
- Reviewed CMDB 360 Denied Classes and the affected CI class is not excluded.
- Observed that cmdb_multisource_data is not synchronized with the current CI values.
- What process refreshes or updates records in cmdb_multisource_data?
- If the CI and source values are correct but cmdb_multisource_data contains stale values, what is the recommended way to refresh the multisource data?
- Are there any known issues or troubleshooting steps for CMDB 360 multisource data not synchronizing with current CI values?
Any guidance would be appreciated.
Thanks!
0 REPLIES 0
