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.
|
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.
Figure 1 : The detailed diagnosis of the IdleOracleSessions Test