Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Oracle Home Problem

11 views
Skip to first unread message

Salaam Yitbarek

unread,
Jun 28, 2002, 4:37:11 PM6/28/02
to
I just re-installed Oracle client and cannot connect to the databases.
tnsping to the machine works, but to the resident databases does not.

-----
C:\>tnsping CORPRDB

TNS Ping Utility for 32-bit Windows: Version 8.1.7.0.0 - Production on
28-JUN-20
02 16:32:29

(c) Copyright 1997 Oracle Corporation. All rights reserved.

TNS-03505: Failed to resolve name
-----

The tnsnames.ora is correct (same as before). I suspect it's a problem
with my Oracle home, even though I only have one. I don't think it's
getting to the tnsnames.ora.

Any suggestions?

Salaam

Daniel Morgan

unread,
Jun 28, 2002, 5:01:04 PM6/28/02
to
Salaam Yitbarek wrote:

The following is the only suggestion on metalink:

Check the INIT.ORA and the LISTENER.ORA files to make sure that the cases
match.

I don't see how it could relate to the client but give it a try. You might
want to peer into the registry and see how things are set but if you are
not familiar with it don't touch.

Daniel Morgan

Ikarus

unread,
Jun 28, 2002, 5:07:42 PM6/28/02
to
When you have more than one tnsnames.ora File, you should set the TNS_ADMIN
.....


Peter Häusler
OCP DBA
peter.h...@dbconcepts.at
www.dbconcepts.at


Rauf Sarwar

unread,
Jun 29, 2002, 1:51:58 AM6/29/02
to
yit...@yahoo.com (Salaam Yitbarek) wrote in message news:<77439c33.02062...@posting.google.com>...


Check your sqlnet.ora file in ORACLE_HOME\network\admin folder. Check
value for NAMES.DEFAULT_DOMAIN, Either

1) Add your domain name specified for above value to your alias name
in tnsnames.ora file e.g. if the value specified is YOURDOMAIN.COM
then add CORPRDB.YOURDOMAIN.COM to your alias in tnsnames.ora file
then try tnsping CORPRDB

OR

2) Comment out NAMES.DEFAULT_DOMAIN in sqlnet.ora file and then use
exact alias name including .domain name in your connection string.
e.g. If NAMES.DEFAULT_DOMAIN is commented out OR there is no
sqlnet.ora file present and your alias is listed as
CORPRDB.YOURDOMAIN.COM then use full name when connecting e.g. tnsping
CORPRDB.YOURDOMAIN.COM

HTH
//Rauf Sarwar

Salaam Yitbarek

unread,
Jul 8, 2002, 2:13:53 PM7/8/02
to
Yes, the sqlnet.ora file was the culprit. Commenting out the
NAMES.DEFAULT_DOMAIN entry did the trick.

Thank you.

rsa...@ifsna.com (Rauf Sarwar) wrote in message news:<c2d690f2.0206...@posting.google.com>...

0 new messages