- NetIQ AppManager 8.0.x
- NetIQ AppManager 7.0.x
- NetIQ UNIX Agent 7.1
- NetIQ UNIX Agent 7.0.1
In some rare circumstances (generally more complex RAQ setups), the OracleUNIX instance updating (aka OracleUNIX MO configuration) may not properly pick up all Oracle databases on the UNIX system in question. This is generally due to the wide range of possible Oracle configurations. You can manually specify which Oracle instances are present on the system which will give you tighter control of the Oracle database instances monitored by NetIQ.
Create an empty file at <netiq>/AM/mo/config/oracle.netiq. This file is created during the OracleUNIX MO configuration (or by running OracleUNIX_UpdateInstances post-discovery) The oracle.netiq file is used by the Discovery_OracleUNIX knowledge script.
The format of this file should be as follows. You specify one database instance per line for the instances you wish to monitor. If you are unsure about this information, you can utilize /etc/oratab and lsnrctl status for assistance (or contact your DBA)
Oracle grouping. Used to match similar oracle major release versions. The number starts at 1 and moves forward. For example, if you have Oracle 11g2 databases and 10g2 databases, all the 10g2 databases would get a 1, and the 11g2 databases would get a 2
Oracle home path for this instance.
The database name / instance.
The hostname or IP where the TCP listener can be reached for this instance. Must resolve on the local UNIX system.
The port of the listener for this instance.
The name of the listener for this database / instance. (can be obtained from lsnrctl status)
Here is an example oracle.netiq file:
You should add a username/password to the AppManager Security Manager for for each instance you wish to monitor. Once this is complete, Discovery_OracleUNIX should be run providing the user specified in AppManager security manager. (While Oracle isn't case sensitive, the NetIQ UNIX Agent is. To avoid discovery problems, be consistent with your username and instance name case)