Agents Administration - Tests
 

Configuration of OraRacPgaTest

This test keeps an eye on the memory consumption by the PGA and be proactively alerted administrator if one/more server processes are draining memory from the PGA rapidly.

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

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

  • Specify the variable name of the oracle instance in the ORASID text box.

  • 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 in the PASSWORD text box.

  • Confirm the PASSWORD by retyping it here in the CONFIRM PASSWORD text box.

  • If the value chosen for the ISPASSIVE flag 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.

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

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.