eG Help

This test reports the number and state of sessions of each user who is currently connected to the Oracle database server. Using the metrics reported by this test, administrators can promptly isolate idle sessions, which are a drain on a server's resources. The measures made by this test are as follows:

Measurement	Description	Measurement Unit	Interpretation
Total_connections	The total number of connections currently established by this user on the server	Number
Total_active_count	The number of connections of this user that are currently active	Number	The detailed diagnosis of this measure, if enabled, will provide the complete details of the active sessions of a particular user. Using this information, you can understand how each of the connections were made - i.e., using which program - and from where - i.e., from which host.
Total_inactive_count	The number of sessions initiated by this user that are currently idle	Number	Ideally, the value of this measure should be low. A high value is indicative of a large number of idle sessions, which in turn causes unnecessary consumption of critical server resources. Idle sessions also unnecessarily lock connections from the connection pool, thereby denying other users access to the server for performing important tasks. The detailed diagnosis of this measure, if enabled, will provide the complete details of the idle sessions of a particular user. Using this information, you can understand how each of the idle connections were made - i.e., using which program - and from where - i.e., from which host.
Total_background_count	Indicates the number of background processes that were started when sessions are initiated by this user.	Number	Ideally, the value of this measure should be low. The detailed diagnosis of this measure, if enabled, will provide the complete details of the background sessions of a particular user. Using this information, you can understand how each of the background connections were made - i.e., using which program - and from where - i.e., from which host.
Total_blocked_count	Indicates the number of sessions initiated by this user were blocked.	Number	Blocking occurs when one session holds a lock on a resource that another session is requesting. As a result, the requesting session will be blocked - it will hang until the holding session gives up the locked resource. In almost every case, blocking is avoidable. In fact, if you find that your session is blocked in an interactive application, then you have probably been suffering from the lost update bug as well, perhaps without realizing it. That is, your application logic is flawed and that is the cause of blocking. The five common DML statements that will block in the database are INSERT, UPDATE, DELETE, MERGE and SELECT FOR UPDATE. Ideally, the value of this measure should be low. A high value may cause unnecessary consumption of critical server resources thereby blocking access to potential active sessions. The detailed diagnosis of this measure, if enabled, will provide the complete details of the blocked sessions of a particular user. Using this information, you can understand how each of the blocked connections were made - i.e., using which program - and from where - i.e., from which host.
Total_cached_count	Indicates the number of sessions of this user that were cached for future use.	Number	Ideally, the value of this measure should be low. The detailed diagnosis of this measure, if enabled, will provide the complete details of the cached sessions of a particular user. Using this information, you can understand how each of the cached connections were made - i.e., using which program - and from where - i.e., from which host.
Total_killed_count	Indicates the number of sessions of this user that were terminated due to inactivity.	Number	Ideally, the value of this measure should be low. The detailed diagnosis of this measure, if enabled, will provide the complete details of the killed sessions of a particular user. Using this information, you can understand how each of the killed connections were made - i.e., using which program - and from where - i.e., from which host.
Total_sniped_count	Indicates the number of sessions of this user that were idle for a period more than the profile's maximum idle time while waiting for a client's response.	Number	Ideally, the value of this measure should be low. The detailed diagnosis of this measure, if enabled, will provide the complete details of the sniped sessions of a particular user. Using this information, you can understand how each of the sniped connections were made - i.e., using which program - and from where - i.e., from which host.