Configuration of OraDgLogGapTest

For each destination to which the redo log files are to be archived, this test reports the count of redo log sequences received and the log sequences applied. The number of log sequences that could not be transmitted to the destination are also reported along with the status of the redo logs.

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 this test is to be configured.

• In the PORT text box, specify the PORT at which the specified HOST listens.

• 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 USERNAME text box.

• In the PASSWORD text box, specify the password of the specified database user.

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

• If the value of ISPASSIVE chosen 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.

• To make diagnosis more efficient and accurate, eG embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability.

  • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

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