The Oracle ODBC driver does not recognize any Oracle service that is not defined in the home in which it is installed. For example, if the Oracle home is installed on C:\Oracle\Orahome1 then the ODBC driver recognizes only the services defined in the C:\Oracle\Orahome1\network\admin\tnsnames.ora file. Since the Oracle agent uses the ODBC driver, the agent can only use those services defined in the driver installation path for data collection.
The ODBC driver automatically points to the home path installed first. If you have multiple homes, the Oracle agent usually does not read the services defined in the last home. To make sure the agent reads the services you create with the Oracle Registration Wizard, the wizard calls the Oracle agent to create the service. The agent then creates the service in the tnsnames.ora file that is present in the path where ODBC driver is installed.
Note: In some configurations the last created home can have the same path as the driver. For example, if you have Oracle 8i installed and later install 9i, the agent will read the driver installed in the 9i home.
When you have Oracle 8i and Oracle 9i installed on a system, the Oracle agent reads Oracle 9i only. The Oracle agent discovers the services defined in the installation folder of the Oracle 9i ODBC driver. If there are any other Oracle homes on the system other than the one with the Oracle 9i ODBC installation, the Oracle agent does not discover the services defined in them. When a service is created using the Oracle Registration Wizard, the service definition will be written to only the tnsnames.ora file that is accessible using the Oracle 9i ODBC driver.
When you have multiple Oracle 10g server installations on multiple homes, the discovery is done on the home whose entry is the first key present in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE (this represents the Oracle home). The service definitions are read from the tnsnames.ora file pointed to by the first key representing the Oracle home. Any new service that the Oracle agent creates (through the registration wizard) will be created in this tnsnames.ora file present in the home pointed to by this registry key.
When the proxy collector machine has both the Oracle9i and Oracle10g client installed, there is only one Oracle ODBC driver available on that system. Under these circumstances the available ODBC driver is the Oracle9i. For successful connection to the Oracle database using the ODBC driver, the system path variable must have the path to the Oracle 9i client before the path to the Oracle 10g client.
Note: CA SRM might fail to collect data successfully from an Oracle 10g server in the following scenario. There are multiple homes of Oracle 10g present on the server machine and the proxy collector that was selected for data collection is the Oracle server itself. To avoid potential failure in such a case, select a different proxy collector machine.
|
Copyright © 2016 CA Technologies.
All rights reserved.
|
|