Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Dead Connection Detection (DCD) on win nt system

Re: Dead Connection Detection (DCD) on win nt system

From: Paul Drake <drak0nian_at_yahoo.com>
Date: 21 Mar 2003 13:28:51 -0800
Message-ID: <1ac7c7b3.0303211328.51943b1f@posting.google.com>


"Bud Socks" <bud_socks_at_gmx.de> wrote in message news:<b5f5dc$28mehj$1_at_ID-2182.news.dfncis.de>...
> Hi there,
>
> according to Oracle note # 151972.1 DCD does not work on windows nt systems
> (for my understandings)
>
> "...Dead connections are cleaned up only when the server is rebooted and the
> database is restarted..."
> It is further stated in this note: to find out how well DCD works on NT
> depends on the client`s
> protocol implementation.
> What does that mean ? For my opinion the DCD does not work at all if the
> server has to be rebooted ! Or
> is it just a question of configuration ? As i mentioned - we are talking
> about windows nt systems.
>
>
> Thank you
>
> Bud

basically, a process is limited to having 16 timer threads under it. since its highly likely that you'd have more than 16 threads under the oracle.exe process, a *nix-like timer is not possible in the Win32 environment.

There are metalink docs that discuss this in further detail.

I believe that you are better off using resource limits, limit the idle time and use a batch job in the OS to spool a kill script using "orakill". alter system kill session does not do the trick - kill the thread first.

Paul Received on Fri Mar 21 2003 - 15:28:51 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US