Re: Dead Clients with SQL*Net and TCP/IP

From: Anton Dischner <dischner_at_med.uni-muenchen.de>
Date: 1995/08/28
Message-ID: <dischner-2808951133350001_at_gkc12a.klch.med.uni-muenchen.de>#1/1


Hi Guenter,

enter tcpctl -?

the standard timeout is set to 0 seconds (off).

Try to set it to a reasonable time.

Please drop me a note if this (and what value) solves your problem.

Hope this helps,
best regards,

Toni

In article <41rnmr$2t60_at_news-s01.ny.us.ibm.net>, brorsg_at_ibm.net (Guenter Brors) wrote:

> When an MS-Windows client crashes or the PC is turned off without
> properly ending the application, the session on the Oracle server
> remains forever open. This is a waste of ressources, apart from DBMS
> locks that may also be held forever and block other users.
>
> It seems that the underlying TCP/IP is used by SQL*Net without the
> KEEPALIVE option, which could help in detecting dead clients. Is there
> any way to turn on this option ?
>
> I do not want a DBA to regularly check on the server side and manually
> kill dead sessions. I want an application that can turn 24 hours a day
> without administration.
>
> I'm using Oracle 7.1.16 on RS/6000 and SQL*Net 2.0 with Pro*Cobol and
> ODBC on MS-Windows.
>
> Please let me know how you solved this problem.
>
> ==================================================
> Guenter Brors - Consultant Client/Server Solutions
> Internet: brorsg_at_ibm.net
> CompuServe: 100137,2305
> Phone: +49(40)6913629 Hamburg
> ==================================================
 

-- 
A. Dischner
Institut fuer Klinische Chemie
Klinikum Grosshadern
Ludwig Maximilians Universitaet Muenchen
Marchioninistr. 15 81366 Muenchen 49-89-70953202
Germany
Received on Mon Aug 28 1995 - 00:00:00 CEST

Original text of this message