Be polite to the Group as a professional. Re: ora817 client access problems. Net8 test ok, but TNSPing does not work.

Sybrand,

First of all, I would like to share one things with you. After painfully comparing tnsnames.ora(client), listener.ora(server), sqlnet.ora(client) among our old oracle server and the window95/98/nt client, I could make my oracle8.1.7 client work (meaning db connection to db server, client vb oo4o application all works)If I manually add an entry key entry "TNA_Admin" with value of tnsnames.ora's directory "..\network\admin" under the right oracle Home entry in the client machine's registry (regedit). it's ok for global_name or just sid, or naming client service aliase anyway you specify.

Still the whole setting is a little itchy, not straitforward, certainly not a recomended stardard solution. I will keep searching to see if it's defected installation disk, or my lacking of full understanding about this client connectivity issue, or maybe a oracle bug they need to fix it.

Oracle dababase is nothing but a customerizable/configturable client-server application like we build all the time on the database end. The client connectivity stuff should make simple as earlier versions. software vendors tend to add some gui puffy stuff to add to their sales, sometime lost of track of end users' core interest. In my opinion, client just need to provide server IP address, database oracle server instance name on this server, (1521 is industry standrard default network logical port for oracle software), that's all. Now the configuration is just too much. Keep this/that in syn, this role/that rule, This is good in another sense to keep DBA employed... ...

We would like to place incident_ call to oracle offical help to get the bottom of this. But my employer is willing to pay me overtime, not the outside source, strange or not.
 We did not experience problems with ora7 families, up to 8.05 as far as I know.

I feel a little offended by your responding attitude, though. we all experience once for a while lost in the documentation of all software vendors. Sometime, people just need a fresh eye/mind to diagnosis the tech problems in another prospective. Pre-judging things could comprises one's professional integrity at a very cheap price.

Now relating to my tech problems, I post all the relevant messages just let peope WHO ARE ENJOYING TO SOLVINGING PROLBEMS have a whole picture. "does not work" IN THE CONTEXT of my posting barely means tnsnames.ora, sqlnet.ora, etc do not work in conert, no client connectivity to the server, and .ora files are posted.

Setting a global name for an db instance at the SERVER SIDE is a user's choice,oracle recommend global_names, db_domain (so you have a db name as unique as your server machine's ip). Setting a names.default_domain at the CLIENT SIDE in the designated sqlnet.ora file would force you to name all your service names ending with this "default_domain" suffix, not desiable at all time. Also I presume this has nothing to do with the server db_domain for a db instance since one client could establish db connections for more than one IP address that host the oracle db server. Consistence here ? sid.db_domain (Initsid.ora, server file)and names.default_domain(sqlnet.ora, on client side) are different concepts. correct me if i am wrong.

"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message news:<trk991k0s4tqd2_at_news.demon.nl>...
> You seem to make a sport of not posting error messages.
> How do you think anyone can help you out?
> Please refrain from comments like
> 'doesn't work'
>
> What doesn't work????
> ERROR MESSAGES, PLEASE!!!
>
> You seem also to make a sport of not reading documentation.
> You should either use the SID (for *pre 8i* software)
> or the *service_name* (parameter in init.ora, which defaults to the global
> database name, which is db_name||'.'||db_domain)
>
> You are inconsistent with respect to using domains,
> in the o1 instance you use a domain in the global database name,
> however you don't seem to use any domain for the other instances and you
> don't use a names.default_domain in sqlnet.ora
>
> How do you expect this is going to work????
>
> Regards,
>
> Sybrand Bakker, Senior Oracle DBA
>
>
> "simon gu" <guxinhong_at_yahoo.com> wrote in message
> news:ae637542.0110020621.680f5b8b_at_posting.google.com...
> > I tried to trace the activity on the client side. however, no *.trc
> > found in the specified directory. by the way my db server is win2000
> > server. How to make tracing work on ora817 client?
> >
> > now this time, please focus on the instance o1.
> > another oberservation is: If I use sql*net 8.05 client to connect to
> > oracle817eent server, everything (tnsping, sqlpus, etc ) works ok
> > using just SID instead of global_nameon the client side. So questions
> > are still in the client side. I need to make ora817 client work
> > concerning the version compatibilities down the road. where do I
> > need to pay attention to this stuff?
> >
> >
> > the two files are copies below. please comment.
> >
> > thanks.
> >
> > /********************sqlnet.ora**************************/
> > # SQLNET.ORA Network Configuration File:
> > C:\oracle\ora81\NETWORK\ADMIN\sqlnet.ora
> > # Generated by Oracle configuration tools.
> >
> > trace_level_client = 16
> > trace_directory_client = C:\oracle\ora81\network\trace
> > trace_unique_client = true
> >
> >
> > NAMES.DIRECTORY_PATH= (TNSNAMES, HOSTNAME)
> >
> > SQLNET.CRYPTO_SEED = 4fhfguweotcadsfdsafjkdsfqp5f201p45mxskdlfdasf
> >
> >
> >
> >
> >
> >
> >
> /****************************listener.ora*********************************/
> > # LISTENER.ORA Network Configuration File:
> > c:\oracle\ora81\NETWORK\ADMIN\listener.ora
> > # Generated by Oracle configuration tools.
> >
> > LISTENER =
> > (DESCRIPTION_LIST =
> > (DESCRIPTION =
> > (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
> > )
> > (DESCRIPTION =
> > (ADDRESS = (PROTOCOL = TCP)(HOST = goldfinger)(PORT = 1521))
> > )
> > (DESCRIPTION =
> > (ADDRESS = (PROTOCOL = TCP)(HOST = goldfinger)(PORT = 2481))
> > (PROTOCOL_STACK =
> > (PRESENTATION = GIOP)
> > (SESSION = RAW)
> > )
> > )
> > )
> >
> > SID_LIST_LISTENER =
> > (SID_LIST =
> > (SID_DESC =
> > (SID_NAME = PLSExtProc)
> > (ORACLE_HOME = c:\oracle\ora81)
> > (PROGRAM = extproc)
> > )
> > (SID_DESC =
> > (GLOBAL_DBNAME = o1.goldfinger.syr.edu)
> > (ORACLE_HOME = c:\oracle\ora81)
> > (SID_NAME = o1)
> > )
> > (SID_DESC =
> > (GLOBAL_DBNAME = o2)
> > (ORACLE_HOME = c:\oracle\ora81)
> > (SID_NAME = o2)
> > )
> > (SID_DESC =
> > (GLOBAL_DBNAME = o3)
> > (ORACLE_HOME = c:\oracle\ora81)
> > (SID_NAME = o3)
> > )
> > )
> >
> >
> >
> >
> >
> > "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message
> news:<9p51t0$gmscl$1_at_ID-62141.news.dfncis.de>...
> > > "simon gu" <guxinhong_at_yahoo.com> wrote in message
> > > news:ae637542.0109290821.58160ca0_at_posting.google.com...
> > > > hmmm, I tried both global_name, and ora8 compatible sid. Both still do
> > > > not work. Should I pay any attention to the sqlnet.ora.
> > > > I presume a client net8 app parses TNSnames.ora for oracle server
> > > > connection info, any other files or configturation tool that I need to
> > > > pay attention.
> > > >
> > > > help, help...
> > > >
> > > >
> > > > "Van Messner" <vmessner_at_bestweb.net> wrote in message
> news:<tr76d4btglu35f_at_corp.supernews.com>...
> > > > > try using a qualified servicename in your tnsnames.ora instead of
> that
> sid
> > > > >
> > > > > "simon gu" <guxinhong_at_yahoo.com> wrote in message
> > > > > news:ae637542.0109271305.41a7cb88_at_posting.google.com...
> > > > > > Net Assistant test ok, but command line login does not
> > > > > > work. connectivity problems
> > > > > >
> > > > > > hi, gurus,
> > > > > >
> > > > > > I could install ora817 client on win2000 pro. Using
> > > > > > Net8 assistant, I could setupa servicing name, and
> > > > > > test it just ok.
> > > > > >
> > > > > > however, it does not work on command line: sqlplus
> > > > > > scott/tiger_at_o3. The Error is ORA_12154: TNS could not
> > > > > > resolve service name.
> > > > > >
> > > > > > and also sqlplus will not connect to the servrer,
> > > > > > using scott/tiger, host_string: o3. the same error
> > > > > > message.
> > > > > >
> > > > > > The related 2 .ora files are print in part for
> > > > > > refereces.
> > > > > >
> > > > > > please offer your suggestions and any hints. thanks
> > > > > > in advance.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > tnsnames.ora --------------
> > > > > > O3 =
> > > > > > (DESCRIPTION =
> > > > > > (ADDRESS_LIST =
> > > > > > (ADDRESS = (PROTOCOL = TCP)(HOST =
> > > > > > goldfinger)(PORT = 1521))
> > > > > > )
> > > > > > (CONNECT_DATA =
> > > > > > (SID = o3)
> > > > > > )
> > > > > > )
> > > > > >
> > > > > >
> > > > > > sqlnet.ora-----------------------------------
> > > > > > #SQLNET.ORA Network Configuration File:
> > > > > > C:\oracle\ora81\network\admin\sqlnet.ora
> > > > > > # Generated by Oracle configuration tools.
> > > > > >
> > > > > > SQLNET.AUTHENTICATION_SERVICES= (NTS)
> > > > > >
> > > > > > NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME)
> > >
> > >
> > > Pleaseb enable tracing.
> > > Add to your sqlnet.ora
> > >
> > > trace_level_client = 16
> > > trace_directory_client = <any sensible directory>
> > > trace_unique_client = true
> > >
> > > Post : the resulting cli*.trc
> > > Your *listener.ora*
> > > Note: an unbalanced parenthesis on any location in tnsnames.ora will
> result
> > > in 12154.
> > >
> > >
> > > And yes: I don't agree with Ban Spam there are various methods to
> connect.
> > > I do agree with him the 3 files have to match.
> > >
> > >
> > > Hth,
> > >
> > > Sybrand Bakker, Senior Oracle DBA
Received on Wed Oct 03 2001 - 09:08:13 CDT