Configuration of OraAsmDiskSpaceTest

This test closely monitors how each disk in a disk group uses the space available to it, points you to the disks that are running out of space, and thus holds a mirror to space contentions on a disk group.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

• The port number to which the oracle server is listening is to be provided in the PORT text box.

• By default, this is set to none, indicating that the test, by default, runs a SQL query to pull out the space usage related metrics from the ASM. If you want the test to execute a script that exists in the ORACLE_HOME directory to extract the desired metrics, then, specify the full path to the ORACLE_HOME directory against the ORACLEHOME parameter. The ORACLE_HOME is the directory where you choose to install the software for a particular Oracle product - in the case of this test, the Oracle database server. The directory that you specify in the ORACLEHOME text box, should be a sub-directory of the Oracle base directory. For instance, your ORACLEHOME specification on a Unix platform can be: /u01/app/oracle/product/10.2.0/db_1. On Windows, the ORACLEHOME can be: D:\oracle\product\10.2.0\db_1.

• Specify the name of the user with rights to access the ASM instance being monitored in the USER text box. This user should also have SELECT privileges to v$asm_disks.

• Specify the password of the specified USER in the PASSWORD text box.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• If the ISPASSIVE parameter is set to YES, then it means that the Oracle server under consideration is a passive server in an Oracle cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable” by the agent if the server is not up.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the Update button will register the changes made.

When changing the configuration for specific servers, a "*" beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a "$" or contain a series of "*". A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.