Default Parameters for OraRacAlertTest

This test periodically tracks the errors that are newly added to the alert log of the target Oracle Cluster database server.

This page depicts the default parameters that need to be configured for the OraRacAlertTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• The variable name of the oracle instance is specified in ORASID textbox.

• A ServiceName exists for the entire Oracle RAC system. When clients connect to an Oracle cluster using the ServiceName, then the cluster routes the request to any available database instance in the cluster. By default, the SERVICE NAME is set to none. In this case, the test connects to the cluster using the ORASID and pulls out the metrics from that database instance which corresponds to that ORASID. If a valid SERVICE NAME is specified instead, then, the test will connect to the cluster using that SERVICE NAME, and will be able to pull out metrics from any available database instance in the cluster.

  To know the ServiceName of a cluster, execute the following query on any node in the target cluster:

  select name, value from v$parameter where name =‘service_names’

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

• Provide the password of the specified database user in the PASSWORD textbox.

• Confirm the PASSWORD by retyping it in the CONFIRM PASSWORD textbox.

• Enter the specific patterns of alerts to be monitored in the SEARCH PATTERN textbox. 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.

• Provide a comma-separated list of patterns to be excluded from monitoring in the EXCLUDEPATTERN text box. 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.

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

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.