Default Parameters for 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.

This page depicts the default parameters that need to be configured for theOraAsmDiskSpaceTest.

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

• 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.

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

When changing default configurations of tests, the values with "$" indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to "xyz" and $port will be changed to "80" when configuring a test.