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: Client Setup

Re: Client Setup

From: GreyBeard <Fuzzy.GreyBeard_at_gmail.com>
Date: Sat, 05 Mar 2005 13:48:44 GMT
Message-Id: <pan.2005.03.05.14.49.32.837500@gmail.com>


On Fri, 04 Mar 2005 21:50:18 -0800, BayAreaKen wrote:

>
> What information do I need to get from the server in order to define
> the client so that it connects?
>

You dare to ask for the arcane secrets of the Oracle Networking connection? you DARE? YOU DARE?????

Ok ... aside from the docco, where you find a lot of variants, try the following to kick off your thought processes. (For the following SQLNet, Net8 and Oracle Networking are synonymous.)

[To the pros: this is but an overview, but corrections appreciated).

  1. starting connection

App -> SQLNet 'client' -> network -> Listener ...> service

b) after connection established

App -> SQLNet client -> network -> 'user process'

Client uses TNSNAMES.ora to find where the service is. Optionally it uses SQLNET.ora to make global assumptions about the entries and methods in TNSNAMES.ora

Listener, which must run in the background, uses LISTENER.ora (and possibly service self-registration) to determine which services (databases) for which to listen.

When listener detects a request from client, it asks service to connect to the client. In *nix that usually means initiating a separate process, finding a spare port, telling the client and the 'user' process to talk on that port, and getting out of the way. (Other variants include port sharing most common on WIndows, but the listener still gets out of the way.)

So, to answer your question:

on client, you need TNSNAMES.ora and optionally SQLNET.ora. You also need an app (SQLPlus, ODBC, etc.) that can connect to the SQLNET client software. You need host resolution (hosts file or DNS) and networking that knows how to access the server.

on server, you need LISTENER.ora, a running listener and preferrably a running database service,

STRONGLY encourage you to try to set this up using the Oracle Network Config Assistant (sw = netca) on both the server side and (at least the first one) the client side. It does help with the niggly syntax issues and has a 'test connection' button.

g'luk/FGB Received on Sat Mar 05 2005 - 07:48:44 CST

Original text of this message

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