Idle Oracle Sessions Test

Inactive sessions to an Oracle database server are serious resource-drainers! Such sessions do not execute any transactions, but consume resources significantly, thereby depriving critical database-related operations of the resources. Idle sessions should hence be identified promptly and terminated quickly, so as to prevent the unnecessary locking of resources.

The Idle Oracle Sessions test keeps an eye out for idle sessions, and alerts administrators as soon as an idle session is detected. This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick Oracle Database as the Component type, Performance as the Test type, choose this test from the disabled tests list, and click on the << button to move the test to the ENABLED TESTS list. Finally, click the Update button.

Target of the test : An Oracle server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every instance of an Oracle database.

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. inactive period - Specify the duration (in minutes) of inactivity beyond which a session is considered to be “idle” by this test. By default, this parameter takes the value 10 (minutes); this implies that by default, the test counts all sessions that have been inactive for over 10 minutes as idle sessions.

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

Current idle sessions:

Indicates the number of idle sessions; note that all sessions that have been passive beyond the INACTIVE PERIOD configured for this test will be counted as idle sessions by this test.

Number

Ideally, the value of this measure should be 0. A high value indicates that a number of sessions are idle and using up resources unnecessarily.

Using the detailed diagnosis of this measure, you can quickly identify the idle sessions and terminate them, so that resources are released for the use of critical processes. Alternatively, you can set a lower idle time in the user profile, so that the user session automatically aborts upon reaching the set idle time.

oraidlesessiontest-DD-final

Figure 1 : The detailed diagnosis of the IdleOracleSessions Test