Re: How to disconnect "dead" client process
Date: 1996/08/22
Message-ID: <4vh2hg$6j3_at_mari.onr.com>#1/1
SQL*Net V2.2 has a dead connection detection mechanism implemented
in it (KEEPALIVE) that is supposedly part of SQL*Net, not the platform's
tcp/ip stack. You might want to look into upgrading to 2.2. Sounds like
it would solve your problem.
Regards,
In article <4vdcq6$2go_at_maverick.tad.eds.com>,
hopper_at_tocv01.pad.navp.gmeds.com says...
>
>Hi -
>
>We are running Oracle SQL*Net version 2.1.4 on our PCs to access an
>Oracle 7.1.6 server on an HP-UX 10.01 machine. These PCs connect via
>Novell Lan Workplace version 4.1.2.
>
>The plant floor users of this system typically log in (through a
>Powerbuilder GUI front-end) and let the screen stay up most of the day.
>At the end of the day, they just power down their PCs (or reboot),
>rather than performing a graceful disconnect from Oracle. This leaves
>Oracle background processes on the HP which not only look alive and well
>to Oracle, but in turn exhaust the site's concurrent license limit. Is
>there anyway to detect that a PC has been powered off/rebooted and
>disconnect that process from Oracle automatically? I know that I can set
>an inactivity limit and have users disconnected when they have been
>inactive for a certain period of time, but that will not be acceptable
>given the way the users utilize this system.
>
>Any ideas you have will be greatly appreciated!
>
>Wendy
Received on Thu Aug 22 1996 - 00:00:00 CEST