Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Head scratching with SQL*Net V2
vqh_at_dw.lucent.com (Viet Q. Hoang) wrote:
>
>The local setup is we have a Oracle server and 2 client machines
>all running 7.1.4, the connections are set up with tnsnames.ora
>and listener.ora for SQL*Net V2 communications over tcp/ip. There's
>only 1 instance on the server.
>
>Yesterday, the dba added another instance on the server and added
>the appropriate entries in tnsnames.ora and listener.ora to make
>it accessible over the net. On client1, things work just as intended,
>on client2 we can not connect to the new instance (but the old instance
>works fine). The error code is ORA-12203 or sometimes ORA-12535.
>
>The server configuration seems ok because we can access both instances
>from client1. The client tnsnames.ora on client2 seems to be ok
>too because it can access the original instance just fine. We stripped
>the tnsnames.ora down to just one entry for the original instance,
>made sure it works and made sure that's the one being used by forcing
>TNS_ADMIN environment variable. After that, we simply changed the
>SID name in the tnsnames.ora to the new instance to make sure there's
>nothing wrong with the entry. That still gave us the same results.
>
>We're stumped, any suggestions on what we might have missed?
My first thought is to turn off automatic IPC in the sqlnet.ora file.
AUTOMATIC_IPC = OFF If that doesn't do it, try turning on tracing. Add or replace the following line in the SQLNET.ORA file on the client.
TRACE_LEVEL_CLIENT = ADMIN When the connection fails, examine the trace file to see what's really happening.
HTH
-- Chuck Hamilton chuckh_at_dvol.com This message delivered by electronic sled dogs. WOOF!Received on Fri Oct 25 1996 - 00:00:00 CDT