Configuration of OraTranWorkloadTest

This test reports how many key database operations - eg., data modifications, block changes, reads/writes, parses, rollbacks, etc. - are performed on the server per transaction. This way, the test reveals the real workload of the server.

The default parameters associated with this test are:

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

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

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

• 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 oraeg identified by oraeg container=current default tablespace default temporary tablespace temp;

  Grant connect, resource to oraeg;

  Grant select_catalog_role to oraeg;

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