Oracle Session Resource Usage Test

In the database context, the connection between the user process and the server process is called a session. The server process communicates with the connected user process and performs tasks on behalf of the users.

This test tracks the resource usage of each session to the Oracle server and thus sheds light on the resource-intensive Oracle sessions. You can also use the detailed diagnostics provided by the test to understand why a user session is consuming CPU/memory resources excessively and then try to attack the problem source.

Note:

  • This test will not report metrics for an Oracle 12c CDB server.
  • This test does not apply to Windows platforms.

Target of the test : An Oracle 10g database server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the 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. DETAILED DIAGNOSIS – To make diagnosis more efficient and accurate, the eG Enterprise 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

Maximum CPU used by a session:

Indicates the percentage of CPU utilization that is the highest among all the sessions of this Oracle server.

Percent

A high value indicates that one/more Oracle sessions are  consuming CPU excessively. Use the detailed diagnosis of the CPU used by Oracle sessions measure to know which session is consuming maximum CPU. Using this session information, you can optimize the query executed by that session to minimize CPU usage.

CPU used by Oracle sessions:

Indicates the percentage of CPU that is currently utilized by all sessions of this Oracle server.

Percent

Maximum memory used by a session:

Indicates the percentage of memory utilization that is the highest among all the sessions of this Oracle server.

Percent

A high value indicates that one/more Oracle sessions are consuming memory excessively. Use the detailed diagnosis of the Memory used by Oracle sessions measure to view which session is consuming maximum memory. Using this session information, you can optimize the query executed by that session to reduce memory usage.

Memory used by Oracle sessions:

Indicates the percentage of memory that is currently utilized by all sessions of this Oracle server.

Percent