
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2020 02:17 AM
Hi All,
I am getting this issue with Oracle database instances discovery where database instances are getting discovered without instance name. This issue i am getting when using patterns.
Its difficult to identify database without name as there can be more than one instances on one host
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2020 12:07 AM
Thanks for confirming, this is an open issue only in Newyork version and we fixed in Orlando.
Actually the wrong identification section is getting executed because of the LINUX os type check.
Kindly remove the LINUX os type check as this identification section is mean to run only on Solaris OS. So remove that condition so that proper 2nd identification section runs.
Save and publish the pattern, After syncing pattern with mid try running fresh discovery on your linux machine, you should not see this issue anymore.
We have a KB article as well for the same.
https://hi.service-now.com/kb_view.do?sys_kb_id=551d275bdb7bcc98414eeeb5ca96196f

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2020 06:20 AM
Hi
Thanks for your reply.
Now i tried with root access and those errors are gone however i still dont see SID name appending.
When i test this on pattern directly. I see everything getting populated correct but when run discovery, same thing does not populate on DB instance record.
There are two dynamic configuration which i dont see running on discovery - which actually captures SID which is used later to set display name.
And there is one error i see in log but i think that is more to capture log and not valid for CI update.
Please see attachments below. Would really appreciate if you can help.
2: Patter Testing
1: from Identification for Oracle DB entry
2: Discovery Pattern Log

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2020 06:27 AM
Hi
Would be great help if you can check this and help me with what i doing incorrect. When i test using pattern directly i am getting all the values but when run discover for oracle instances name is populating without SID prefix
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2020 10:32 AM
Usually, I see what Andrew went through, permission errors. However, if you are seeing that the values are coming back and you have full access then, without being able to see it directly, I'd suggest opening an incident with support. They should be able to get to the problem directly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2020 11:30 AM
Hi Santosh,
I want you to just confirm me some things.
- Is it Newyork version?
- Is this "Identification for Oracle DB entry point type(s) - no instance on solaris" Identification section getting executed as part of "Oracle DB on Unix" pattern execution when you run the Linux server horizontal discovery? You can check this in pattern log in Discovery Log from the Discovery Status record.
- In "match we are on solaris" pattern step from above identification section in "Oracle DB on Unix" pattern is there any condition matching to "LINUX" os type?
Let me know if you have any queries.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2020 11:57 AM
Hi Sid, yes ..answer for all your question is YES. when i use debugger i get all the details for DB instance with correct name (SID + @hostname) however when discovery job runs its creating record with only @computer hostname