Oracle Alerts Test

This oracle-specific test periodically tracks the errors newly added to the Oracle alert log.

Note:

This test will not report metrics for an Oracle 12c PDB server.

Target of the test : An Oracle server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every alert log file.

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. alertfile  - By default, this is set to none, indicating that the eG agent auto-discovers the path to the Oracle alert log file to be monitored. If required, you can manually specify the full path to the alert log file to be monitored. For eg, /user/john/alert_egurkha.log 
  5. 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.

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

  7. Confirm password – Confirm the password by retyping it here.
  8. searchpattern - Enter the specific patterns of alerts to be monitored. The pattern should be in the following format: <PatternName>:<Pattern>, where <PatternName> is the pattern name that will be displayed in the monitor interface and <Pattern> is an expression of the form - expr or expr or expr or expr, etc. A leading ‘*’ signifies any number of leading characters, while a trailing ‘*’ signifies any number of trailing characters.  

    For example, say you specify ORA:ORA-* in the SEARCHPATTERN text box. This indicates that “ORA” is the pattern name to be displayed in the monitor interface. “ORA-*” indicates that the test will monitor only those lines in the alert log which start with the term “ORA-“. Similarly, if your pattern specification reads: offline:*offline, then it means that the pattern name is offline and that the test will monitor those lines in the alert log which end with the term offline.

    Multiple search patterns can be specified as a comma-separated list. For example: ORA:ORA-*,offline:*offline*,online:*online.

    Specify all if all Oracle alerts are to be monitored.

  9. lines - Specify two numbers in the format x:y. This means that when a line in the alert file matches a particular pattern, then x lines before the matched line and y lines after the matched line will be reported in the detail diagnosis output (in addition to the matched line). The default value here is 0:0. Multiple entries can be provided as a comma-separated list. 

    If you give 1:1 as the value for LINES, then this value will be applied to all the patterns specified in the SEARCHPATTERN field. If you give 0:0,1:1,2:1 as the value for LINES and if the corresponding value in the SEARCHPATTERN filed is like ORA:ORA-*,offline:*offline*,online:*online then:

    0:0 will be applied to ORA:ORA-* pattern

    1:1 will be applied to offline:*offline* pattern

    2:1 will be applied to online:*online pattern

  10. exclude pattern - Provide a comma-separated list of message patterns to be excluded from monitoring. For instance, if you want to monitor all alert messages that begin with “ORA-“, except the messages that begin with    “ORA—“ and “ORA-info”, you can configure ORA-* as the searchpattern and configure ORA--,ORA-info as the exclude pattern.
  11. 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.
  12. DETAILED DIAGNOSIS – To make diagnosis more efficient and accurate, the eG Enterprise suite 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

Recent errors:

Indicates the number of new errors that have been written by oracle to the alert log file.

Number

The value of this measure is a clear indicator of the number of “new” alerts that have come into the alert log of the monitored database.

File size:

Indicates the current size of the alert log file.

MB

This measure will only be reported for the ‘Summary’ descriptor of this test.

Growth rate :

Indicates the rate at which the alert log file is growing

 

MB/Sec

This measure will only be reported for the ‘Summary’ descriptor of this test.

A high value for this measure or a consistent increase in its value indicates that the alert log is rapidly growing and may end up occupying too much space on the volume.

Under such circumstances, it is recommended that you delete the alert log file and then issue a log file switch, so that Oracle automatically creates a new alert log file for you the next time a database activity needs to be logged.