From: otierney@freenet.edmonton.ab.ca ()
Subject: Re: Linking IP address to Oracle process
Date: 1996/11/02
Message-ID: <55fu2i$nh4@news.sas.ab.ca>#1/1
references: <32733F38.24B8@access.net.au> <327705f8.1045772@n5.gbso.net> <55bcnh$g95@cdn_news.telecom.com.au>
organization: Edmonton FreeNet, Edmonton, Alberta, Canada
newsgroups: comp.databases.oracle,comp.databases.oracle.server



[I have not heard of  lsof , but it sounds useful]
I do not know what you are trying to do, but setting the sqlnet tracing
to 16 in sqlnet.ora , for either client and/or server will probably give you
all you need [trussing the client process will give you similar information].

If you really need to know in advance what tcp socket you are going to use,
there are a couple of ways to set up oracle so the server side processes
[not just the listener ] are already listening before you connect, and 
you can use netstat -a , or sqlnet trace files[?], to see what they are 
listenung on: 
1/ use dispatchers [set up in init.ora lsnrctl services gives some info]
2/ use prespawned servers [set up in listener.ora - on unix AVOID in normal
                           operation]

Turloch