Use the Discovery_OracleUNIX Knowledge Script to discover instances of Oracle RDBMS.
To successfully discover Oracle configuration and resource information, you must use the AppManager Security Manager extension to specify the Oracle user, password, and the Oracle database instance names you want to monitor. Also, the account with which you run this script must have SELECT permissions for the following tables:
DBA_DATA_FILES
DBA_SEGMENTS
DBA_TABLESPACES
DBA_USERS
V_$DATABASE
V_$INSTANCE
V_$VERSION
By default, this script runs once for each computer.
Set the Values tab parameters as needed.
|
Description |
How to Set It |
|---|---|
|
Oracle Username |
Enter the Oracle RDBMS username used to access the target databases. If you run this script on more than one computer, configure each database with the same username. The default value is blank. NOTE:To use SYSDBA authentication, leave the Oracle Username parameter blank. |
|
Discover instances not automatically started on system boot? |
Select Yes to discover Oracle instances not started by the dbstart utility upon system boot. This information is obtained from the oratab file. By default, these instances are discovered. |
|
Keep version number in root node? |
Select Yes to keep the version number in the root node of the discovered tree. The default is unselected. NOTE:If this option is unselected, the discovered tree does not contain the version number of the Oracle database appended to the root node name. Without the version number attached to the discovered tree, an Oracle module update, when there is a database upgrade, happens seamlessly. If the option is selected, the version number is a part of the root node name. |
|
Raise event when discovery fails? |
Select Yes to raise an event when discovery fails. By default, events are enabled. |
|
Event severity when discovery fails |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The default value is 5. |
|
Raise event when discovery partially succeeds? |
Select Yes to raise an event when discovery is partially successful. By default, events are enabled. |
|
Event severity when discovery partially succeeds |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The default value is 30. |
|
Raise event when discovery succeeds? |
Select Yes to raise an event when discovery succeeds. By default, the job does not raise events. |
|
Event severity when discovery succeeds |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The default value is 40. |