Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

New Toad Version - TNS unable to resolve name 1

Status
Not open for further replies.

JaxtheDog

Programmer
Oct 3, 2002
37
US
I got a new version of Toad version 9.1, and since then I cannot connect to my Oracle databases and get the message -TNS could not resolve service name.

I am using the same TNSNAMES.ORA which worked before, and it is in the right location i believe ( becos i can select the database read from the TNSNAMES file). Also I can tnsping the host name, but cannot connect thru TOAD or SQL Plus.

Does anybody have a clue to what I am missing?

Thanks
 
Confirm that your applications (TOAD and SQL*Plus) are pointing to the correct PATH for your Oracle Home and that inside your Oracle Home, the tnsnames.ora file is in the /network/admin subdirectory.

Let us know your findings.

[santa]Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]
 
Thank you for your help--the quick reply is much appreciated. We did check the Oracle_home variable and it was missing. It is hard to say for sure, since we tried several things and could have been better testing after each, but it appears that the presence of a sqlnet.ora in the same directory (C:\oracle\ora92\network\admin) as the tnsnames.ora caused a problem. When we renamed it, the problem (unable to resolve service name) went away--and the person who did it is fairly certain it was after the fix to the Oracle_home did not resolve the issue. Is there any way that a bad sqlnet.ora could interfer with Oracle finding the correct tnsnames.ora?

Anyway, we are up and running again. Thanks!
 
Jax said:
Is there any way that a bad sqlnet.ora could interfer with Oracle finding the correct tnsnames.ora?
An incorrectly specified sqlnet.ora could absolutely, positively goof things up.


Following are the contents of my sqlnet.ora on my PC. (My contents might not be the same that your implementation requires, and the contents of a Unix sqlnet.ora differ from the contents below for my PC.):
Code:
TRACE_LEVEL_CLIENT = OFF
sqlnet.authentication_services = (NTS)
names.directory_path = (TNSNAMES, HOSTNAME)
names.default_domain = world
name.default_zone = world
automatic_ipc = off
So, don't just copy the above over to your sqlnet.ora. But note that if I eliminated or changed the setting of any one of the above specifications, it could interfere with my successfully connecting to a target database.


[santa]Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]
 
Thank you for the reply--and for your help! It is much appreciated

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top