Re: Orphan sessions
Date: Fri, 24 Jun 2011 18:59:03 +0200
On 22.06.2011 22:28, joel garry wrote:
> On Jun 22, 10:33 am, David Budac<davidbu..._at_gmail.com> wrote:
>> I guess I have to figure out why SQLNET.EXPIRE_TIME didn't work. We've
>> had this parameter set. The more I read about it, the more I see it
>> was supposed to work. The protocol in use is TCP which makes it even
>> Thanks again
> I seem to recall this can happen if the oracle user process has
> spawned a child, the child dies or gets hung up in a wait (or odd
> things that put errors in the alert log), and the parent waits forever
> for the child to respond, ignoring the death signal from the client.
> Or something like that.
As far as I remember Oracle's architecture in Windows versions they do not use multiple processes with shared memory there but rather a single process with a thread per connection (which would be the dedicated server process on *nix).
-- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/Received on Fri Jun 24 2011 - 11:59:03 CDT