eG Help

Database administrators should eye sessions that have been open for a long time suspiciously, as such sessions are often indicators of performance bottlenecks. By zooming into such sessions, administators can identify inefficient queries, hung/unresponsive transactions, or session logout failures that may be causing the sessions to remain open for abnormal time periods. This investigation may also bring inactive sessions to light. Inactive sessions unnecessarily hold on to critical server resources, causing business-critical transactions to fail for want of resources! To quickly isolate such problem sessions and the users who initiated them, and to rapidly determine the reason for the problems, administrators can use the OraLoginSessTest.

This test tracks user logins to the database server, identifies users who have sessions open for over a configured duration, and reports the count of such sessions per user. Using the detailed diagnosis of this test, you can also figure out the status of each session. This way, administrators will not only be able to determine the number of sessions that are ‘suspect’, but can also drill down to the reason why the sessions have been open for an unreasonable period of time. In addition, by reporting session status, the test also leads administrators to inactive sessions that are needlessly draining critical server resources.

Measurement	Description	Measurement Unit	Interpretation
Session_count	Indicates the number of sessions for this user that have been open for a duration beyond the configured USER LOGIN TIME.	Number	A high value indicates that the user has too many sessions open for an abnormal period of time. By comparing the value of this measure across users, you can quickly identify the user who has the maximum number of such sessions. To know what is causing the sessions to be open for such broad time windows, use the detailed diagnosis of this test. The detailed diagnosis reveals the session start time, the machine from which the session was initiated, the program/query executed in the session, and the session status. From this information, administrators can figure out whether a long-running query / inefficient query is causing the session to remain open for a long time. Such queries can be terminated to close them. Also, by looking at the session status in the detailed diagnosis, administrators can ascertain whether/not the session is active. Once a session is identified as inactive, administrators can proceed to terminate the session, to release critical server resources.