
- 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-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
05-11-2020 09:04 AM
Did this solve your problem?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2020 08:10 AM
Hi Sid, thanks a lot. Yes it worked.
May i ask one more thing - actually i am able to discover Oracle Instances on Solaris Server (these are super clusters)
My technical team say - they cant install "lsof" command on Solaris super cluster.
Is there any other way to discover Oracle DB Instances on solaris servers - would be great help if you can direct me on this. Most of DB instances in our env are on these super clusters
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2020 09:13 AM
Thanks for informing, good that it resolved your issue.. 🙂
Your comments are little confusing, you said you are able to discover instance on solaris super cluster and what is the issue again you asked any other way of discovery?
Also i'm not much aware of this and I couldn't make out what you need exactly from your comments, soo can you elaborate on your requirement and what is your concern reg the lsof command in this context?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2020 12:15 PM
Sorry i meant NOT able to discover Oracle Instances on Solaris Server (these are super clusters) ..sorry for typo.
The fix you suggested helping me to get discover oracle instances on Linux servers.
in our environment we have super clusters (Solaris Servers) and Oracle DB Instance running on those - not able to discover those DB instances. None of DB records shows up when i discover those solaris servers. For oracle do instance discovery in servicenow doc there is requirement of having access to comman lsof (Disco ALL=(root) /sbin/lsof)
We dont have access for this command - is there any other way to discover ?