ugg classic short boot UGG Australia Boots ,slippers and sandals online

Implemented in Oracle 8x automatically disconnected and reconnectedIn the actual database applications, we often encounter such a problem connecting to the Oracle database user made an operation, no subsequent operations, but for a long time did not disconnected from the database. For a small application system is concerned, a limited number of connections per se, it does not seem any serious consequences, but if for a large database applications. Such as taxation, industry and commerce, the number of connections a lot if the database for the database server is concerned, we must consume more than one connection to a resource, and if a large number of users connect into the database system but do not carry out any operation, this invisible to causing the server vain waste of system resources, while causing increased load on the server, for those who do the work in terms of users, can not maximize the use of server resources, in severe cases may result in a sharp decline in performance against this problem , how to handle it? For the popular three-tier structure (Browser / Application / Server) develop speaking, this problem can set the application server connection shared pool (shared pool) to be avoided. But for the traditional two-tier structure (Client / Server) application, we must by human intervention to avoid this waste of resources situation. Specifically through a background task to monitor all processes in the system, for those idle for more than a certain time in the process to take certain special treatment measures, such as the client prompts the user to connect a long time, if there is no follow-up the operating system will automatically kill the connection or directly kill the idle connection. Below on to discuss how the Oracle 8x environment to achieve user processes automatic monitoring and studies of the connection idle time exceeds a certain approach to achieve automatic background tasks idle connections over a certain time processing, the first step is to work from all connection with the database server to identify those connections need to be addressed, which is the need to get connected to the server for each user's login time after the last operation of idle time. In Oracle system, there is a dynamic performance view v $ session, the view of the preservation system is currently connected to a variety of dynamic information. Among them, there are two fields LOGON_TIME and LAST_CALL_ET can get the above two answers l LOGON_TIME is a date type (Date) field, landing time for users;l LAST_CALL_ET is a numeric type (Number) field, and its meaning is the end user a statement after the implementation of the time, in seconds. Each time the user performs a new statement, this field is reset to 0 to start counting. We can use this field to get a connected user database after the last operation idle time following SQL query can be obtained with the current database connection for all users some basic information, such as user name, status, connect the machine name, operating system the user's name, UNIX system process ID, the UNIX operating system level disconnected statement, Oracle database system disconnected statements, landing time, and the last operation to the current idle time, etc. In the above query, We can SUBSTR (machine, 1, 19) NOT IN ('machine name') this condition to shield some of the machines that may need to take a long time to run some SQL statement or some other special cases of the machine. The reason is that these machines shield in the background behind the automatic recognition and processing tasks on these machines without treatment two, to identify and disconnect idle users stored procedureThe above query system can be connected to all of the user's basic situation, but how to implement the system automatically determine the connection idle for more than a certain time and automatically disconnect it? Call Oracle system provides a background task (Job) automatic processing mechanisms. We can write a background task to regularly perform in order to determine whether there is such a user is connected, if it exists, by the background task will automatically disconnect its first create a stored procedure to spare some time to complete the identification and disconnect users work, then Add a background task to time (determined according to the length of idle time) perform this procedure, you can automatically disconnect the system idle time to the user's needs over a certain stored procedures p_monitor below, where the parameters an_nimutes for the user input parameters used to determine the Identify and disconnect multiple users connected to a long idle time, in minutes, the default is 60 minutes, which is one hour. Point to note is that the stored procedure, you need to run as the sys user. Accordingly, the call to the stored procedure background tasks also need to add as SYS.