Outside Discovery Issue

[Former Member]

Hi,

I am having an issue with the outside discovery process and it not detecting the database installed on a logical host.We have a scenario where we have one physical host with two SAP systems installed. The first has been installed using the physical hostname of the server and the second has been installed using a logical hostname, a seperate diagnostic agent has been installed for each of the hostnames (physical and logical). The diagram below shows the layout:

The host discovery process has detected both the physical and logical hostnames and pushed the host data to the LMDB. The database data for the system installed on the physical hostname has been pushed to the LMDB however for the database installed on the logical hostname it has not.

When running the command, "saphostctrl -function listDatabases" on the server it does not list the database installed on the logical hostname but does find the database installed on the physical hostname. If i run the command "saphostctrl -function getDatabaseProperties -dbname <SID> -dbtype ora" using the SID of the system installed on the logical hostname the values are returned successfully. The same applies when running "saphostctrl -function getDatabaseStatus -dbname <SID> -dbtype ora".

I have tried updating the hostagent to the latest version (720 patch 112) and the kernel of the Diagnostic's Agents but this has not resolved the issue. I have also applied SAP Note 1712468 but this has not resolved the error. Our Solution Manager version is 7.1 SPS4, both the Databases for the managed systems are Oracle 10.2.

Thanks in advance for any help

Ryan

[Former Member · Accepted solution]

Hi,

Just a quick update on this issue just in case anyone else comes across the problem. The issue is now resolved, I raised it with SAP and they provided a solution. The issue was caused by the Oracle home of the second database not being contained within the Oracle central Inventory.

If you experience this issue check the value of /var/opt/oracle/oraInst.loc, I found firstly this was pointing specifically to one of the Oracle Homes (/oracle/<sid>/...) rather than /oracle/oraInventory changing this value back resulted in the other database being installed. I believe the value of /var/opt/oracle/oraInst.loc had been amended during previous installs due to the suggestions in note 350251. This resulted in the central inventory missing the new Oracle Homes.

To add the missing Oracle Homes to the central inventory the following command had to be run as ora<sid>.

runInstaller -attachHome ORACLE_HOME="<Oracle_Home_Location>" ORACLE_HOME_NAME="<Oracle_Home_Name>"

The steps to resovle the issue are:

1) If required point /var/opt/oracle/oraInst.loc to the Central Inventory

2) As ora<sid> navigate to ORACLE_HOME/oui/bin

3) ./runInstaller -attachHome ORACLE_HOME="<Oracle_Home_Location>" ORACLE_HOME_NAME="<Oracle_Home_Name>"

Once this has been completed the database should be detected by the host agent, the process is similar for Windows environments however the paths to the files and the commands are slightly different. The below Oracle help pages contain the information:

Oracle 10.2:

http://docs.oracle.com/cd/B19306_01/em.102/b16227/oui3_manage_oracle_homes.htm

Oracle 11.2:

http://docs.oracle.com/cd/E11882_01/em.112/e12255/oui2_manage_oracle_homes.htm

Ryan