Sqlnet 2.1 leaves session alive after user reboots resulting in record locking.
Date: 1996/07/16
Message-ID: <4sgqpn$n0i_at_dfw-ixnews7.ix.netcom.com>#1/1
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? Received on Tue Jul 16 1996 - 00:00:00 CEST