Hello,
We have a similar situation with our Win2K terminal server-based sessions and our Win2K database server (8.1.7.4.1) although we have not introduced the use of SQLNET.EXPIRE_TIME in this case. As detailed in Metalink Doc ID 151972.1 (Dead Connection Detection (DCD) Explained), there are limitations in a Windows environment. These limitations are not restircted to a Windows-only environment however, as I have seen the same behaviour with NT4 terminal servers connecting to an AIX database server (8.1.7.2.1). The use of DCD is worth investigating. Other Metalink documents that may be useful are 1018160.6 (Common Questions About Dead Connection Detection (DCD)) and in particular, check out bug 2167389 (THREAD LEAK WITH DCD SET CAUSES NT TO HANG) If you discover that that DCD introduces more problems than it solves, then it is trivial to disable - simple hash out the SQLNET.EXPIRE_TIME parameter in the SQLNET.ORA file - no reboot required. HTH --- nigel. > Hi Guys , > we have forms/report application installed on windows terminal > servers and user access application from these terminal servers . > When some session hangs on these term server adminstrator resets > those sessions . But the corresponding database session remains > alive . > Is it s problem with some sql*net setting ?? Any help in this > regard is highly appreciated . > -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: nigel cemm INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
