Re: HELP: SERVER MANAGER CANNOT CONNECT
Date: 1996/10/02
Message-ID: <52tr7f$3qa_at_dub-news-svc-8.compuserve.com>#1/1
Richard Woods <rawoods_at_concentric.net> wrote:
>Steve Chell wrote:
>>
>> We're running Oracle Server Manager version 2.0.4.0.0
>> for Windows 3.1, and it's having problems connecting to
>> a database.
>>
>> When I specify a service name in the Connect dialogue
>> box, it responds with the following:
>>
>> MGR-02073: an error occurred while
>> connecting to a database
>> ORA-12154: TNS:could not resolve service
>> name
>>
>> If I *don't* supply the service name, it successfully
>> connects to the default database (prod).
>>
>> This is weird, because I'm sure our TNSNAMES.ORA file
>> is correct, because Browser can successfully connect to
>> both service names.
>>
>> Has anyone else encountered this problem? Or more to the
>> point, anyone know how to fix it???
>>
>> Thanks in advance,
>>
>> Steve Chell
>> slc_at_stevensons.co.nz
>Steve,
>The 12154 implies exactly what it says - couldn't find the service name
>in your tnsnames.ora. But it could also be a couple of other things.
>You need to have a listener running on the host you're trying to connect
>to, you need to have the service defined in the listener.ora file as
>well as tnsnames.ora, and the service name must be defined exactly the
>same way in both files, ie., mydb.world.
>Because you said you're running Windows 3.1, I've ignored any other
>issues related to simultaneously running 16-bit and 32-bit SQL*Net
>clients.
>--
>Rich Woods
>Technical Field Support Specialist, Oracle Corporation, USA
>The above statements and opinions are my own and do not
>necessarily represent those of Oracle Corporation.
Besides checking the above,
This was Oracle support's 'solution' to our problem. Not very pretty
but it did work. You might want to give it a try.
you might try the Oracle TNSPING facility
to double check your connect and tnsnames file parameters. Also we
ran into a problem (on the client - windows 3.1) using SQL*NET
2.3.2.1.3 where if we put the host name (ie. HOST=myserver) in the
HOST= parameter of the tnsnames file, the host name (service) 'could
not be resolved'. When we put in the IP address (ie.
HOST=123.345.56.678) in the HOST= parameter, the service was found.