Extended CMDB Tables Show Wrong Application Scope After Moving Update Sets
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2025 06:54 AM
Hi all,
I’m working with a custom application and have both a development and test instance. I’ve transferred all the relevant update sets with customer updates from the custom app to the test instance.
However, when I inspect the Dictionary in the test instance, I notice that some extended tables of the cmdb_ci table have their Application set to my custom app scope, whereas in the development instance they are correctly set to Global.
This wasn’t the case in the development environment, so it seems something went wrong during the update set import or commit.
My question is:
How can I correct the Application scope of these extended CMDB tables in the test instance back to Global?
Any insights or best practices on handling this are very much appreciated!
Thanks in advance,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2025 06:55 AM
For example the sys_class_name