sqlnet.expire_time = <seconds of inactivity>,
where <seconds of inactivity> - interval to check if client session is alive
I would also recommend you to consider profiles where you can limit both idle and total time for user connections.
Resource parameters you need to set in profiles are
After that you need to assign new profile to the user(s)
whose connect time you need to limit.
There was one thing I noticed about the sqlnet.expire_time:
'Dead connection detection is not allowed on bequeathed connections'
I use MTS and was wondering what they mean by 'bequeathed connections'?
I'll start making the changes anyway.
Thanks for your reply,
Bequeth protocol is used for local connections, so in this case (with local connections) dead connection detection will not work. In your case with MTS there is no limitation for DCD (dead connection detection), so you may safely use it.