Re: Sqlnet 2.1 leaves session alive after user reboots resulting in record locking.

David Shaw wrote:
>
> When a user is updating a record and their PC locks up and must be
> rebooted, Sqlnet 2.1 doesn't recgnize they are no longer connected,
> resulting in the record staying locked. When the user gets back in,
> they can't update the record. I know there were problems with Sqlnet
> 1.1, but I thought that these problems were fixed in version 2.x of
> Sqlnet.
>
> We are running Oracle and Sqlnet on a SCO server and connecting
> over TCP/IP from a Windows PC.
>
> Oracle's solution is to kill the session either at the operating
> system level or with the server manager. There must be a better
> solution, preferably one that would prevent the problem in the first
> place. Have we overlooked something and not set up, or configured
> Sqlnet properly? Is there a time out function to automatically clean up
> lost connections?

Have u tried setting the 'expire_time' in the sqlnet.ora. If not set this on both the client and the server to any reqd. value.This should take care or ur problem (hopefully !).
Take a look in to ur ORACLE_HOME/network/doc/README.doc

Good luck

Mohan
DBA
John Deere
ou90764_at_deere.com