- 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
02-13-2020 05:40 AM
Are these clustered oracle instances where the oracle process is not running but the tnslsner is? I had this happen recently where a Change on the inactive node is a cluster went from Implement to Review; this kicked off a ServiceDiscoveryProbe; It found the tnslsnr running on port 1521; but because this was now the inactive node in the cluster there was no pmon processes running, so it fell through to "Lightweight Identification For Oracle DB". If it makes it here the only thing it does is create the oracle CI without the SID.
So a couple of questions here. What is the Discovery Source for the instance? If it is CredentiallesDiscovery then it likely fell through to the Lightweight Identification noted above.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2020 05:39 AM
Thanks Duane for input but seems that's not the case as its able to find running process.
<parameter value="{"tcp_port" : "","running_process_key_parameters" : "","running_process_command" : "ora_pmon_SNPFWP1","running_process" : "953b9c93dbba801088c41847489619ed","pid" : "18783" }" name="process_info"/>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2020 07:28 AM
Hi,
We have had something similar here and fixed most of the issues this week. Look at my attached images. Check the most recent server discovery and for an Oracle discovery click "Here". Even though the discovery shows green, it was full of failed commands, mostly "ls" and "cat".
It seems that SN test their software under lab conditions where they have full admin rights to do everything. We needed to get our Linux gurus to add new "sudo" rights and also read permissions of various directories.
Hope this helps
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2020 05:49 AM
