cmdb_ci_cloud_org table is corrupted
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
After installing CMDB plugins like class models and service mapping, the table:
cmdb_ci_cloud_org
is missing its name(label) and also dismissing all its IRE entries.
This causes any Discovery to fail, as the pattern is not able to identifiy any IRE entries for this table and its extended ones.
Has anyone experienced anything similar?
Currently we are engaged with SN HI support, and awaiting for resolution.
Any takers?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hi @Mariano Lemus ,
What you're seeing with cmdb_ci_cloud_org losing its label and IRE entries after installing the CMDB CI Class Models and Discovery and Service Mapping Patterns plugins is actually a known issue in ServiceNow (KB0831487).
This table, which represents IBM Cloud Organizations, can get impacted during plugin installation or upgrade. The issue occurs because the table ends up being created using a Table-Per-Class (TPC) structure, whereas CMDB is designed to work with a Table-Per-Partition (TPP) model. Due to this mismatch, the table loses its label and all IRE entries, which in turn breaks Discovery patterns.
To confirm whether your instance is affected, you can navigate to the sys_storage_alias table and look for records where the table name is cmdb_ci_cloud_org. Then check the storage table name. If it shows values like cmdb or cmdb$par1, the table is healthy. If it shows cmdb_ci_cloud_org itself, then the table is impacted.
There isn’t a generic fix or script available for this issue. Each case requires a backend correction tailored to the specific instance, so continuing to work with ServiceNow HI Support is the correct approach.
If your sub-production instances are also affected, you can resolve them by cloning from a clean production instance, provided production is not impacted.
When working with HI Support, it helps to reference KB0831487 and share the results from the sys_storage_alias check so they can diagnose and fix it faster.
Hope this helps.
If it helped you please do mark it as helpful and accept the solution
Thanks,
Vishnu