Re: HP-UX running out of Processes : ORACLE??

Perhaps I'm missing something.
>
> If expire_time=10, does this not mean that Oracle's SQL*Net V2.x
> will 'house-keep' a noted dead connection, using a probe packet, after
> ten minutes? Where does the concept of '1Hour of idle time' enter
> into the picture.
> PB
>
There are two ways of controlling hanging connections. The SQLNET dead connection detect depends on a failure of the SQL*NET connection and typically works on a ten minute limit as indicated above. This can fail if a client user has an application failure and uses Control/ALT/Delete to clear the application. IF the system is not rebooted then SQL*NET will likely consider the SQL*ction valid and will respond correctly to probes. However, if the user reboots the system then the connections will likely be correctly identified as dead.

The other method is to the use the idle time parameter in the PROFILE. This one is more typically set to one hour. Unfortunately, if a user connection is left idle for two hours the connection is maintained until the user hits a carriage return, then he gets a message that he has been idle too long and only THEN will the database let go.

Marek Wiechula Received on Sat Sep 14 1996 - 00:00:00 CEST