Configuration of OraListenerLgTest

Using this test, you can not only determine whether listener logging is enabled or not, but also continuously track the usage of space by the listener log file, so that you can detect any rapid growth in log file size early and take adequate measures to curb the growth.

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.

• In the HOST text box, specify the host for which the test is to be configured.

• Specify the port 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 <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.

• Specify the full path to the install directory of the Oracle database server in the ORACLE HOME text box. For instance, on Unix, your path specification can be: /u01/app/oracle/product/9.0.2.

• By default, none is set against the LISTENER LOG DIR text box indicating that the eG agent will discover the exact location in which the listener.log file resides.

• In the LISTENER NAME text box, specify the name of the Oracle listener service associated with the managed Oracle instance. By default, this parameter is set to none. This means that by default the test will attempt to connect to and check the status of the ‘default listener’. However, if the server has been configured using a ‘named listener’, then you should change the value of the LISTENER NAME parameter. If not, then the eG agent will generate a false alert on the Lsnr_availability measure.

• If the ISPASSIVE parameter is set to YES, then it means that 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.