Shulou(Shulou.com)06/01 Report--

ORACLE session timeout

Since the database migration, the connection to the database has always prompted the session to be unavailable. It is only when communicating with customers that they know that their program to connect to the database has been connected since the morning, and several operations need to be performed in a day. Due to the time-out limit of the session connection in the database, the client will be disconnected if there is no operation for a long time. After this event, some Oracle settings for timeout exit are summarized: 1 profile's idle_time limit 2 profile's connect_time limit 3 sqlnet's expire_time limit 4 sqlnet's INBOUND_CONNECT_TIMEOUT_listener_name limit 5 listener's CONNECT_TIMEOUT_listener_name limit

1 idle_time profile restricts the password policy of oracle users' profiles to take effect in real time, WYSIWYG. However, the resource limit of the user profile is determined by the resource_limit parameter. The unit is minutes. If you remember correctly by default, it should be 10 minutes. If the modified resource takes effect, you need to set resource_limit to true alter system set resource_limit=true. If the user does not perform any action within the time of idle, he will be prompted ORA-02396:exceeded maximum idle time. The default connect_time limit of please connect again 2MagneProfiles is UNLIMITED. The unit is minutes when the user cannot continue the operation after arriving at the setting. He will prompt ORA-02399: exceeded maximum connect time, you are being logged off if it is set for 1 minute, and he will remind you to log in again in nearly 2 minutes. 3 expire_time restriction of expire_time: expire_time mainly detects whether the client can be connected at a specified time, and rescheduls if possible, otherwise it will be disconnected and encountered during the execution of rman: ORA-03135: connection lost contact, you can try to set this value higher. (ID 729811.1) 4 the inbound_connect_timieout_listener_name limit unit of inbound_connect_timieout_listener_name sqlnet is seconds, and the default value is 60 Use the INBOUND_CONNECT_TIMEOUT_listener_name parameter to specify the time, in seconds, for the client to complete its connect request to the listener after the network connection had been established. If the listener does not receive the client request in 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 has not received client's request 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 an 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, you can set INBOUND_CONNECT_TIMEOUT_listener_name to 2 seconds and INBOUND_CONNECT_TIMEOUT parameter to 3 seconds. If clients are unable to complete connections within the specified time due to system or network delays that are normal for the particular environment, then increment the time as needed. If the client does not connect to the database within the specified period of time, ORA-12525 will appear in the listener.log log, and an error will be reported in the alert log on the connect_timeout_listener-name limit of ora-03136 5 listener, which is rarely used

CONNECT_TIMEOUT_listener_name=number

This parameter sets the number of seconds that the listener waits to get a valid SQL*Net version 2 connection request after a connection has been started. The listener drops the connection if the timeout is reached. Default is 10; if set to 0, it will wait forever.

The parameter value is in seconds, and the default value is 10s. If there is no response within the set time after the monitoring is established, the connection will be disconnected. A setting of 0 indicates that there is no wait time limit.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.