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.

Note:

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
  1. TEST PERIOD - How often should the test be executed
  2. Host – The host for which the test is to be configured
  3. Port - The port on which the server is listening

  4. User – 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.

  5. Password – Password of the specified database user

    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.

  6. Confirm password – Confirm the password by retyping it here.
  7. ISPASSIVE – 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.
  8. includepath - This test reports a set of results for each datafile on the target Oracle database server. This means that every datafile is a descriptor of this test. By default, while displaying the descriptors of this test, the eG monitoring console does not prefix the datafile names with the full path to the datafiles. This is why, the INCLUDE PATH flag is set to No by default. If you want the data file names to be prefixed by the full path to the data files, then, set the INCLUDE PATH flag to Yes.
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.

Number

 

Warning message

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

Number

 

Error message

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

Number

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.

Number