Oracle Databases Instances are getting discovered without instances name

Santosh Kumar8 · ‎02-13-2020

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

SiD2 · ‎04-20-2020

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

Please mark Helpful / Accept Solution so that it helps others with similar questions.

View solution in original post

SiD2 · ‎05-14-2020

So there are 2 things here, before you want to discover oracle instance on solaris server, the horizontal discovery of the server should be done and that solaris server pattern should successfully create server CI.

So from your update I understood oracle DB CIs are not found, but are you not even finding solaris server CIs also?

What about the solaris server horizontal discovery status? Which solaris os version are you using, as we only support 2 version families.

If your solaris server discovery is all good, please share which step is failing for oracle db pattern for solaris server? I don't see the lsof command used in OOB patterns.

There could be like your solaris super clusters not supported with existing pattern but I couldn't find any info in the documentation though.

Let me know these details to assist you further.

Please mark Helpful / Accept Solution so that it helps others with similar questions.

Santosh Kumar8 · ‎05-14-2020

Hi Sid, i am discovering Solaris server but not DB instance running on that. OS version is 5.11

SiD2 · ‎05-14-2020

In your previous comment you mentioned about not able to discover oracle db instances on solaris super cluster, so asked like that.

However now as I see 5.11 means Solaris 11 version family and we are supporting this version. But as said earlier in OOB pattern lsof command is not used anywhere.

I see this screenshot is of server CI, soo what exactly is your issue when I can see the solaris server is getting discovered.

Please mark Helpful / Accept Solution so that it helps others with similar questions.

Santosh Kumar8 · ‎05-14-2020

This is Host Server ..what about application running on this host? in this case Oracle DB Instance ..i dont see those getting discovered like Linux host where i get both Linux server and DB instances running on it too

DuaneNMore · ‎05-14-2020

So I am trying to understand the current situation. You have Oracle DB Instances running on Solaris. As I understand it the Oracle DB Pattern never gets kicked off, is that correct?

If this is the case, you should look at the classifier. The pattern won't get kicked off if it doesn't classify the process as oracle. go to

Discovery Definition->CI Classification->All

and open up the classifier for "Oracle Instance"

Go down to the Related List "Applications" and look for the process for the oracle instance running on your Solaris Server. If it is not there, then classification is failing. If it is there then take a look at which probes should be launched.