Re: Client Timeout mechanism

From: Al <al_at_work>
Date: 1997/12/10
Message-ID: <01bd0576$309e4340$e9c7e28e@alan_stutchbury>#1/1

The sqlnet.expire time is set at the client side. This parameter directs the SERVER end to periodically check that the client connection still exists. If the connection can not be verified (i.e. application GPF, PC re-boot) then the server side process is terminated.

I do not believe that a similar verification is initiated from the client side.

Jacques Guzy <Jaque_Guzy_at_icomverse.com> wrote in article <3482742D.FB865CFD_at_icomverse.com>...
> Connor McDonald wrote:
>
> > check out: sqlnet.expire_time = 5
> > (mins) in sqlnet.ora on the server
> >
> > Jacques Guzy wrote:
> >
> > > Hi.
> > >
> > > Does anybody know about a way to configure SQL*Net or Net8
> > > so that the connection will timeout after a while, when not
receiving
> > > an answer to a request ?
> > >
> > > My problem is that if the server crashes or the network fails, the
> > > client
> > > application waits indefinitely.
> > >
> > > Thanks in advance
> >
> >
>
>
> Thanks for the help, but my problem is on the client side, not on the
> server
> side.
> If the Oracle instance crashes, my client application immediately gets
> an error message. I would like to have the same thing in case of
> a server crash or a network failure.
>
> Jacques Guzy
> DBA
>
>
>
Received on Wed Dec 10 1997 - 00:00:00 CST