Configuration of OraRacWorkloadTest

At configured intervals, this test compares the usage levels and execution times of all queries that started running on the cluster in the last measurement period and identifies a &lsquotop query’ in each of the following categories - CPU usage, memory usage, disk activity, and execution time. The test then reports the resource usage and execution time of the top queries and promptly alerts administrators if any query consumes more resources or takes more time to execute than it should. In such a scenario, administrators can use the detailed diagnosis of this test to view the inefficient queries and proceed to optimize them to enhance cluster performance.

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

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

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

• 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 default, the SERVICE NAME is set to none. In this case, the test connects to the cluster using the ORASID and pulls out the metrics from that database instance which corresponds to that ORASID. If a valid SERVICE NAME is specified instead, then, 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’

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

  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.

• By default, the detailed diagnosis of this test reports the top-5 queries in resource usage and execution time. This is why, the DDCOUNT parameter is set to 5 by default. If you want detailed diagnosis to display less or more number of top queries, then change the DDCOUNT.

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

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