Configuration of OraRacAsmDskSceTest

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.

• Specify the host for which the test is to be configured in the HOST text box.

• Specify the port on which the server is listening in the PORT text box.

• Specify the variable name of the oracle instance in the ORASID text box.

• By default, this test auto-discovers the full path to the Oracle installation directory. This is why, the ORACLE HOME parameter is set to none by default.

• A ServiceName exists for the entire Oracle RAC system. When clients connect to an Oracle cluster using the ServiceName, then the cluster routes the request to any available database instance in the cluster. By specifying a valid SERVICE NAME, the test will connect to the cluster using that SERVICE NAME, and will be able to pull out metrics from any available database instance in the cluster.

  To know the ServiceName of a cluster, execute the following query on any node in the target cluster:

  select name, value from v$parameter where name =‘service_names’

• By default, the USE ASM INSTANCE flag is set to No indicating that the eG agent is capable of extracting the metrics related to the space utilization of the ASM disks from the ORASID. In some environments, the ORASID may provide outdated metrics. In such cases, set this flag to Yes so that the eG agent can extract the metrics using the name of the ASM instance instead of the ORASID.

• In order to monitor an Oracle database server, a special database user account has to be created in every Oracle database instance that requires monitoring. A Click here hyperlink is available in the test configuration page, using which a new oracle database user can be created. Alternatively, you can manually create the special database user. When doing so, ensure that this user is vested with the select_catalog_role and create session privileges.

  The sample script we recommend for user creation (in Oracle database server versions before 12c) for eG monitoring is:

  create user oraeg identified by oraeg
  create role oratest;
  grant create session to oratest;
  grant select_catalog_role to oratest;
  grant oratest to oraeg;
  

  The sample script we recommend for user creation (in Oracle database server 12c) for eG monitoring is::

  alter session set container=<Oracle_service_name>
  create user <user_name> identified by <user_password> container=current default tablespace <name_of_default_tablespace>
  temporary tablespace <name_of_temporary_tablespace>;
  Grant create, session to <user_name>;
  Grant select_catalog_role to <user_name>
  

  If the USE ASM INSTANCE flag is set to Yes, then, the user monitoring the Oracle database server should be vested with an additional SYSDBA privilege. To provide this privilege, do the following:

  grant sysdba to user <user_name>;
  

  The name of this user has to be specified here.

• Specify the password of the specified database user in the PASSWORD text box.

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

• If the value chosen for the ISPASSIVE flag is YES, then 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 above value is provided, click on the Update button to 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.