Re: ORA-12203

I'd just like to point out that a TNS-12203 error doesn't necessarily mean that there's a problem with the TNSNAMES.ORA file. I'm getting this error when I try to do 16 bit SQLNET connection to a remote database from my Windows 98 desktop. The strange thing is that I have no problem connecting with 32 bit SQLNET. I've read ALL the documentation I can find including a trawl through MetalLink. I KNOW that my config files are Ok becuase they're copies of those from another machine. My theory is that in upgrading to Win98 I have now installed a Winsock that is incompatible with 16 bit SQLNET. If anyone has any suggestions I'd sure like to know.

Thanks

James

On Thu, 7 Jan 1999 14:01:08 +0200, "Billy Verreynne" <vslabs_at_onwe.co.za> wrote:

>Ben Wu wrote in message <76vujv$sso$1_at_hfc.hk.super.net>...
>>When I start SVRMGR39 at dos prompt it shown this error message. Then I
>try
>>to connect to others is still occur.
>>
>>How can I run Server manager at both client and server dos prompt without
>>this message prompt.
>
>
>12203, 00000, "TNS:unable to connect to destination"
>// *Cause: Invalid TNS address supplied or destination is not listening.
>// This error can also occur because of underlying network transport
>// problems.
>// *Action: Verify that the service name you entered on the command line
>// was correct. Ensure that the listener is running at the remote node and
>// that the ADDRESS parameters specified in TNSNAMES.ORA are correct.
>// Finally, check that all Interchanges needed to make the connection are
>// up and running.
>
>
>Pretty self explanatory I think. Some RTFM'ing helps. :-)
>
>You can also use TNSPING to test the TNS alias. I'm sure there's something
>wrong with your TNSNAMES.ORA file.
>
>regards,
>Billy
>
>
Received on Fri Jan 08 1999 - 15:05:29 CST