Default Parameters for OraArchiveAreaTest

This test periodically monitors the usage of the archive log destination directories, and warns administrators about a sudden/consistent decrease in the free space available in the directories. This enables administrators to act fast and free sufficient space in the directories, so as to prevent the database from suspending its activities.

Note:

For this test to work;

• The eG install user should be in the Oracle User Group.

• The database should run in ARCHIVELOG mode

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

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

• By default, the eG agent auto-discovers the location of the Oracle archive log file. This is why, the ARCHIVELOGFILE parameter is set to none by default. If required, you can manually specify the path to the Oracle archive log file to be monitored. For e.g., /user/john/archive

• 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 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 text box, and the password of this user has to be entered in the PASSWORD text box. Confirm the password by retyping it in the CONFIRM PASSWORD text box. 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. 

• If the ISPASSIVE parameter is set to YES, then it means that, by default, all Oracle servers being monitored by the eG system are the passive servers of an Oracle cluster. No alerts will be generated if the servers are not running. Measures will be reported as "Not applicable" by the agent if the servers are not up.

• Once the necessary values have been entered, 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.