Oracle Session timeout Exit settings

Some time ago the customer called to say that since the database was moved after the database is always prompt session is not available, and customer communication to know that their connection to the database program is from the morning after the database has remained connected, a few operations a day, due to the database session connection has a timeout limit, Causes the client to disconnect for a long time without action.

This event summarizes some of the Oracle's settings for timeout exits:

1 profile Idle_time Limit 2 profile Connect_time limit 3 sqlnet expire_time limit 4 s inbound_connect_timeout_listener_name Limitations of Qlnet5 Listener of the connect_timeout_listener_name limit

1,profile idle_time Limit
    The password policy of the Oracle user's profile is in real time, WYSIWYG. However, the resource limits for user profiles are determined by the Resource_limit parameter.
    is minutes, the default is 10 minutes
    If the modified resource is in effect, set Resource_limit to True
     alter system set Resource_limit=true;
     If the user does not perform any action during idle time, it will prompt ora-02396:exceeded maximum idle time, please  Connect again
2,profile connect_time limit
    default is unlimited, in minutes
    Users cannot continue after they have reached the setting , you will be prompted ora-02399:exceeded maximum connect time, you are being logged off
    If it is set for 1 minutes, he will remind you to log back in for nearly 2 minutes.
3,sqlnet expire_time Restrictions:
    Expire_time is primarily to detect whether the client is connected at a specified time, and if so, to re-clock, or to disconnect the
When executing Rman, meet: Ora-03135:connection lost contact, you can try to set this value a bit larger. (ID 729811.1)

Inbound_connect_timieout_listener_name Limitations of 4,sqlnet
Unit is seconds, default value is 60
Use the Inbound_connect_timeout_listener_name parameter-Specify the time, in seconds, for the client-to-complete it S connect request to the listener after the network connection had been established.

If the listener does not receive the client request at the time specified, then it terminates the connection. In addition, the listener logs the IP address of the client and an Ora-12525:tns:listener have not received client ' s Reque St in time allowed error message to the Listener.log file.

To protect both the listener and the database server, Oracle Corporation recommends setting this parameter in combination With thesqlnet.inbound_connect_timeout parameter in the Sqlnet.ora file. When specifying values for these parameters, consider the following recommendations:

• Set both parameters to a initial low value.

• Set the value of the Inbound_connect_timeout_listener_name parameter to a lower value than the sqlnet. Inbound_connect_timeout parameter.

For example, can set Inbound_connect_timeout_listener_name to 2 seconds and inbound_connect_timeout parameter to 3 Seconds. IF clients is unable to complete connections within the specified time due to system or network delays that is normal fo R the particular environment, then increment the time as needed.
If the client does not connect to the database within the specified time, ORA-12525 will appear in the Listener.log log and an error will be given in the alert log ora-03136

5,listener Connect_timeout_listener-name Limited, rarely used

Connect_timeout_ Listener_name= Number

This parameter sets the number of seconds, the listener waits to get a valid Sql*net version 2 connection request Afte R A connection has been started. The listener drops the connection if the timeout is reached. Default is 10; If set to 0, it'll wait forever.

The parameter value unit is seconds, and the default value is 10s, and if no response is set up after listening, the connection will be disconnected. A setting of 0 means there is no wait time limit.

Oracle Session timeout Exit settings