Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.misc -> Re: R: TNS could not resolve service name problem
Have you modified listerner.ora to say that you now have to sids running on the
box. If not
then the request comes in from box B and it can see instance A running (by
reading the
listener params set in listerner.ora).
listerner.ora
LISTENER =
(ADDRESS_LIST =
(ADDRESS=
(PROTOCOL = TCP) (Host = acme.virgin.net) (Port = 2000)
on box B
sqlplus u/p_at_instancea
sqlplus u/p_at_instanceb
"C.A.M." wrote:
> Check if the TNSNAMES.ORA file on serverB has an entry for the instanceB. If > not you should not be able to access the service from ServerB. > > iHiH (I Hope it Helps) :o) > > Jimmy <c6635500_at_comp.polyu.edu.hk> wrote in message > 3817F03D.B2C475D8_at_comp.polyu.edu.hk... > > Hello all, > > > > Two Solaris server, A and B. Oracle 7.3 on server A. > > > > On server A, running sqlplus can connect two instances instanceA and > > instanceB. However, on server B, running sqlplus can only connect > > instanceA and an error message 'TNS could not resolve service name' was > > shown. > > > > How can I make the SQLPLUS on serverB connect to instanceB? Should I > > shutdown the Solaris server after making changes on Solaris server B? > > > > Thanks, > > Jimmy > >Received on Thu Oct 28 1999 - 06:30:10 CDT