Default Parameters for OraSqlNetTest

Using the JDBC API, this test reports the availability and responsiveness of the server, and collects statistics pertaining to the traffic into and out of the database server.

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

• 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 manually creating a user on an Oracle database server before version 10G, ensure that the select_catalog_role and create session privileges are granted to the user. When monitoring an Oracle database server 10G (and above), this test additionally requires select privileges to the sys.user$ table

  The sample script we recommend for user creation (in Oracle database server versions before 10G) 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 version 10G and 11G) 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 select sys.user$ 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 in the USER text box, and the password of this user has to be entered 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.

• The ORACLESID text box, indicates the variable name of the oracle instance. This parameter will not be available while configuring this test for an Oracle Database server. However, it will be available for this test when monitoring an Oracle Cluster service or an External Oracle server.

• If the ISPASSIVE parameter is set to YES, then it means that, by default, all Oracle servers being monitored by the eG system are the passive servers of an Oracle cluster. No alerts will be generated if the servers are not running. Measures will be reported as "Not applicable" by the agent if the servers are not up.

• In the TIMEOUT text box, indicate the duration (in seconds) for which this test should wait for a response from the Oracle Database server. By default, this is set to 60 seconds.

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