- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-17-2022 12:40 PM
I've created a customer Pattern for Discovering Oracle Catalogs in cmdb_ci_db_ora_catalog table.
The Pattern can create a CI in cmdb_ci_db_ora_catalog tabel and also a CI in the Instnace table cmdb_ci_db_ora_instance. That's all fine, but when there is an update of any data found by Discovery, it simply does not update the catalog data.
I can see the data in the Discovery log and verify that it's the new and correct data, but the CI is never updated when Discovery is finished.
The strange thing is that IF I delete the oracle catalog CI or the oracle catalog and the oracle instance that's holding the catalog and run discovery again, the CI is created with the same data as I see in the logs from before - the data that wasn't updated.
By assumption is that this has to do something with the last step that's creating the relations. But I have no more ideas on what the issue might be... ¯\_(ツ)_/¯
Anyone with a good guess here?
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-21-2022 07:13 AM
Looks like only Service Mapping (Discovery Source: ServiceWatch) is allowed to update the Oracle Catalog.
On the Oracle Instance both Discovery (Discovery Source: ServiceNow) and Service Mapping are allowed to update the CI. But they can only update specific fields.
Michael
Please mark the suggestion as helpful/like, if you find it useful to you or others who wants to refer similar content.
Please mark the solution as correct, if the answer provided has resolved your query.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-21-2022 07:13 AM
Looks like only Service Mapping (Discovery Source: ServiceWatch) is allowed to update the Oracle Catalog.
On the Oracle Instance both Discovery (Discovery Source: ServiceNow) and Service Mapping are allowed to update the CI. But they can only update specific fields.
Michael
Please mark the suggestion as helpful/like, if you find it useful to you or others who wants to refer similar content.
Please mark the solution as correct, if the answer provided has resolved your query.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-21-2022 08:05 AM
Wow! I think that was it really!
I got the CI to update now with the value..!
I had NO idea to look here for the issue! Thank you so much
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-23-2022 05:45 AM
OOTB there is no Recon rule . It must be added in your environment.
Regards
RP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-18-2022 10:32 AM
Hi Henrik
Can you share your pattern? I going to need to create a pattern for this Oracle catalogs too.
Thanks
Pedro
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-17-2024 12:23 PM
Hi,
I created a pattern extension and a reconciliation rule to allow ServiceNow to update the Oracle Catalogs, but the extension is not creating/updating the CIs.
If I debug it, I see the values in the variables until the step that populates the [cmdb_ci_db_ora_catalog] table.
The discovery log shows something like this:
Step: Transform Oracle Catalog table
2024-10-17 18:18:32: setAttribute(cmdb_ci_db_ora_catalog,[])
What am I missing here?
Thank you.
