idle time in session

sojan

when we process a report, suppose it may take 2 hours. the idle time in session shows 2 hours. but we need the idle time 0. since the procees is in progress, why the idle time increases. can anybody help.

kine

All depends if there is communication between client and DB server. If you are processing the data only in your temporary table etc., there is no communication and thus the idle time is raising. Try to read something from the DB in some periods to prevent that.

bbrown

Why do you need "Idle Time = 0"? If you ae looking to check if the client is still active then look at "Last Batch". Compare this to current time. It will tell you how long it has been since the client accessed the database.

ssingla

Maybe "Session Killer" is terminating the session and process?

bbrown

ssingla wrote:

Maybe "Session Killer" is terminating the session and process?

My point exactly. A "Session Killer" should be looking at "Last Batch" (compared to current time) not "Idle Time". What it does is look at how long it has been since the connection did something. Not that it's not doing anything now.

kine

"Last Batch" (compared to current time) not "Idle Time"

It is same. Idle Time is calculated as "Current Time" - " Last Batch" .... ;-)

David_Singleton

Or just train the users to log out when they finish working.

Any code you write to avoid training will end out costing more than just training the users.

sojan

bbrown wrote:

Why do you need "Idle Time = 0"? If you ae looking to check if the client is still active then look at "Last Batch". Compare this to current time. It will tell you how long it has been since the client accessed the database.

thanks for your information, but how can we findout the last batch.

kine

You do not need that. It is used in the view to calc idle time. If the session should look like active, it needs to communicate with server.