Re: SQL*Net 2.x configuration

Jason Collison wrote:
>
> L. Tseng wrote:
> >
> > I believe I have configured TNSNAMES.ORA correctly
> > but failed to get serviec name resolved.
> > All I get is
> >
> > ERROR: ORA-12154: TNS:could not resolve service name
> >
> > However, the TNSNAMES.ORA file works just fine on a different server.
>
> Sounds similar to the problem I am having right now. I don't have a
> solution, but I did find a workaround. When I'm connecting to oracle
> locally I must not specify the SID, but when connecting over the network
> I have to. I would think that Oracle would be smart enough to deal with
> the SID when I'm connecting locally, but obviously I'm faily
> oracle-clueless. :)
>
> Like I said, it's just a workaround. Damn inconvenient, too, because
> now if I want to move applications to a remote machine they must be
> recompiled.
>
> Any tips, anyone?

The reason you enter the SID on the network end of it is to allow you to decide where you want to connect to if you have more than one Oracle database. When you run it on the machine it assumes you mean the SID that exists on the one machine. If you had more than one on the box you would again need to specify which instance you want to connect too. Hope that helps. For client machines, use the SQL-net Easy Config tool, it works wonderfully normally. This all assuming you use the SID name for the connect string when you configured it as most people likely do?!

Aside: If you use DNS services on your network then you shouldn't have to recompile every time you move the database to a different machine (assuming you use the same SID).

Anyone else have any thoughts? Received on Tue Dec 30 1997 - 00:00:00 CST