Re: ORA-12203 - only 1 client has problem!

Hi Stephen,

This may sound as a stupid question: did you check the tnsnames.ora of this particular client (assuming you don't use Oracle Names). There may be an incorrect servername in this file.
If you decide to increase connect_time_out (which sounds reasonable), you only need to restart the listener. I have a feeling (I never needed to look at connect_time_out), you can change it in lsnrctl without restarting, so you may be able to experiment.
Finally:
You should give tracing from this client a shot. Put (or change) the following lines in sqlnet.ora on the client

trace_level_client = 16
trace_unique_client= true
trace_directory_client = <anything as long as it is not orawin\bin>

This will dump every call and every sqlnet message to the trace file.

Hth,
Sybrand Bakker, oracle DBA

Stephen Clarke wrote:

> Hi!
>
> I have a new user who is getting "ORA-12203: TNS - unable to
> connect". All my other users are fine. Our LAN people are
> investigating possible "underlying transport" problems (i.e. a faulty
> IntraNetware client installation). We are using Oracle 7.3.2.3 Server
> for Netware and the SPX protocol.
>
> My first question, is there any reason to use Ping if the client's
> network connection is working for other apps (CC:Mail, Web, etc..)? If
> so, how do you ping in a Netware/ SPX environment (i.e. "ping
> ourhost")?
>
> I am also wondering if this error can be triggered if the client "times
> out" (the PC is several routers away in another building)? If so, is
> there any reason not to either bump up or comment out the
> "Connect_Timeout_Listener" parameter in Listener.ora? And if so, what
> are the steps (use NetManager?, Restart the DB?, etc)?
>
> Any other suggestions would also be welcome!
>
> TIA,
>
> Stephen Clarke

Received on Thu Mar 04 1999 - 14:03:06 CST