Oracle Dataguard Errors Test

This test reports the statistical information about the events generated by the target Oracle database server on which the Data Guard feature is enabled.


This test can be executed only on the primary database on which the Oracle Data Guard feature is enabled.

Target of the test : An Oracle server on which Data Guard feature is enabled

Agent deploying the test : An internal/external agent

Outputs of the test : One set of results for every Oracle Database server being monitored.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed


The host for which the test is to be configured.


The port on which the server is listening.


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.

Confirm Password

Confirm the Password by retyping it here.


If the value 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.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise 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 for a particular server, choose the On option. 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 normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Informational message

Indicates the number of information events generated during the last execution of the test.



Warning message

Indicates the number of warning events that were generated during the test's last execution.



Error message

Indicates the number of error events generated in the during the test's last execution.


The detailed diagnosis of this measure lists the Destination ID, error message, the error message number, the error code and the error message.

Fatal message

Indicates the number of critical events that were generated when the test was last executed.