Connection Timeout [message #54202] |
Mon, 04 November 2002 15:32 |
pswar
Messages: 2 Registered: October 2002
|
Junior Member |
|
|
Can someone explain
How oracle manages the client connections?
Does it kill a user session if that user connection is idle for very long time.
What kind of error does it issue when it times out/ kills a user connection.
What parameters in Listner.ora/init.ora are used to control the timeout on a user session.
|
|
|
Re: Connection Timeout [message #54203 is a reply to message #54202] |
Mon, 04 November 2002 18:25 |
andrew again
Messages: 2577 Registered: March 2000
|
Senior Member |
|
|
I think it's possible to set an idle time limit in the profile assigned to an oracle user, but I've never used that. By default, the sever never disconnects a user. In your local sqlnet.ora (wherever your client is) you can set the timeouts. If you use something like OBDC, then it disconnects after a certain time - either set in the odbc admin panel - or you change it in the registry (windows client).
|
|
|
Re: Connection Timeout [message #54208 is a reply to message #54202] |
Mon, 04 November 2002 23:48 |
Trifon Anguelov
Messages: 514 Registered: June 2002
|
Senior Member |
|
|
There are no listener.ora parameters for the timeout. You can use sqlnet.expire_time > 0 in your sqlnet.ora file to enable the DCD (Dead Connection Detection). When you enable DCD then the dead client connections to the listener will be cleaned after the timeout is reached.
To terminate the idle connections, you create a profile, change the IDLE_TIME parameter to whatever minutes you want, add resource_limit = true in init.ora file, assign the user to this profile and the client connections will be terminated after that time. If you have an application, the connection will be terminated and after the first user attempt for any SQL query, DML or DDL the user will receive a message. You can also limit the connect time by the user in the profile too.
Hope that helps,
clio_usa
OCP - DBA
Visit our Web site
|
|
|