Default Parameters for OraOtherFileIOTest

This test auto-discovers the archive log files, redo log files, control files, etc., in the Oracle databases and reports the time taken by the server for processing single block and multiblock I/O requests to each file. This way, the test points you to current/probable latencies when processing  I/O requests to archive, redo log, control files, and others. The exact file, when reading from/writing to which, the latency was maximum can also be identified.

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

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

• 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. This login information is required to query Oracle's internal dynamic views, so as to fetch the current status / health of the various database components.

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

• Specify the Oracle listener name in the LISTENER NAME. By default, this will be the same as the Oracle SID.

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