Re: SQLNET V2 question -Reply

After going to Sql*Net v2.1 from v1, I no longer had old daemons in Solaris left over.

Actually, I can no longer see ANY unix process with the uid of "orauser" like I used to for client connections.

Sql*Net v2.1 includes a timeout parameter in the sqlnet.ora file called sqlnet.expire_time=# of minutes.

Sql*Net v2.2 is very nice but isn't supported by Developer 2000. It works fine on PC but it pukes Dev2000 on Unix. Note also that v2.2 includes a new Network manager 3.0 which is fantastic! It's stable and very easy to use. Network Manager 2.1 outputs files which have syntax errors and is less than friendly.

I highly recommend switching from v1 to v2.1 for production work but would wait on 2.2 if you use unix clients until it comes bundled with Developer 2000.

Hope that helps.

>>> Pete Barnett <pete_at_ALPHA.OIT.OSSHE.EDU>
01/09/96 10:59am >>>
v2 includes dead connection detection - at least in theory. I experienced this problem at a different location with v1, but this was supposed to have been corrected in later v1 releases. Since I left before the newer versions were installed, I don't know if it worked.

Pete Barnett pete_at_alpha.oit.osshe.edu

On Tue, 9 Jan 1996, Tribble Dave wrote:

> We're still on V1 sqlnet and have an ongoing problem with
our PC
> connections. When a PC based client re-boots their PC
during an active
> connection to the database, that session's daemon usually
does not go away
> on the UNIX side and often seems to run away eating up
CPU as fast as
> possible.
> Question: Does anyone out there know how V2 sqlnet
handles this type of
> lost connection?
>
Received on Tue Jan 09 1996 - 15:10:07 CST