I've seen this sort of thing happen when you have more than one Oracle_Home and client
tools get confused about which tnsnames.ora file to use. Fastest solution is to find
every tnsnames.ora file on the client computer and make sure that they are all
identical. Correct solution is usually to m
Open the sqlnet.ora. What is NAMES.DEFAULT_DOMAIN set to. Add that as a
suffix to the DEV_DB entry.
If there is no sqlnet.ora or it has no NAMES.DEFAULT_DOMAIN entry try
adding .world:
DEV_DB.{whatever_names.default_domain_is | world} =
..
At 11:09 AM 1/20/2004, you wrote:
what is the listener s
The previous attachment was filtered out by the ListGuru mailing
software at fatcity.com because binary attachments are not appropriate
for mailing lists. If you want a copy of the attachment which was
removed, contact the sender directly and ask for it to be sent to
you by private E-mail.
This
what is the listener status??
Raj
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD: Any clod can have facts, having an opinion is an art !
-Original Mess
On Tuesday 20 January 2004 11:20 am, Scott Canaan wrote:
> Are you using Oracle Services? I've seen this happen before and we
> change SERVICE_NAME to SID and everything works fine.
That does not work for me either.
RDB
> -Original Message-
> Reuben D. Budiardja
> Sent: Tuesday, January
If you have a line like this on your sqlnet.ora
names.default_domain = world
Then try putting an entry like this in tnsnames.ora
dbname.world=(etc. etc.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: <[EMAIL PROTECTED]
INET: [EMAIL PROTECTED]
Fat City Netwo
Are you using Oracle Services? I've seen this happen before and we
change SERVICE_NAME to SID and everything works fine.
Scott Canaan ([EMAIL PROTECTED])
(585) 475-7886
"Life is like a sewer, what you get out of it depends on what you put
into it." - Tom Lehrer.
-Original Message-
Reube
Reuben,
If the normal connection is throwing an error, then it stands to reason that
the seond one would not connect either. You need to get a connection
working first before you try something else.
The Oracle error you are getting is complaining about the service_name
entry. Is this the same v
Hello,
On Tuesday 20 January 2004 11:01 am, Mercadante, Thomas F wrote:
> Reuben,
>
> If the normal connection is throwing an error, then it stands to reason
> that the seond one would not connect either. You need to get a connection
> working first before you try something else.
I can confirm t
