last_call_et in v$session

[Lily_Liu_2004]

DBAs,

We are trying to identify if we suffer a connection leak problem. The connection pool has been used up We set up the timeout on the connection pool is 30 seconds and a min-size of 0 on most. But when we query the v$session, we found out some user session¡¯s last_call_et is more than 600 seconds.

Does this mean we got a connection leak problem?

Thanks!

[Axr2]

Are these ACTIVE or INACTIVE sessions?

Post the whole query and output.

[hrishy]

Hi

The column last_call_et in v$session tells you how long the inactive sessions were inactive.

You cannot clearly say from here that there is a connection leak.

What middle tier are you using for connection pooling JDBC ? OCI ?

Post the JDBC or OCI code one of us would look at it.

At a place where i contracted the java programmers instead of returning the connection to the pool used to close the connection .And we had some problems with that :-)

regards
Hrishy

[Lily_Liu_2004]

Originally posted by hrishy
Hi

The column last_call_et in v$session tells you how long the inactive sessions were inactive.
Hrishy

Thanks for reply.

Sorry to say that I have the opposite impression that
last_call_et shows you how long the active session has been active. That means It is the time since the last call started and the time since the last call finished.

The query is:

select ses.username
,ses.machine
,ses.program
,ses.last_call_et
,sql.hash_value
,sql.sql_text
from v$session ses, v$sql sql
where ses.sql_hash_value = sql.hash_value
and ses.last_call_et > 600
and ses.type = 'USER'
/

[engiri]

Sometimes I have seen this last_call_et=0 and session status=inactive
for long time.

[mdash]

what abt last_call_et of background process sessions