Re: R: TNS could not resolve service name problem

   And what is CORAENV file? What is the use of this file in Solaris?    By the way, I solve the problem by making change the tnsnames.ora in server B.

Thanks,
Jimmy

Brian Peasland wrote:

> You also might want to check and ensure that your environment variables
> are correct. I've seen this problem where one doesn't have the
> ORACLE_SID set. When trying to connect without an SID, it doesn't know
> which instance to connect to so it can't resolve the service name. I've
> mostly seen this on NT machines. After you set the ORACLE_SID, you'll
> probably need to source the CORAENV file. On our Solaris boxes, it's
> like (in CShell):
>
> setenv ORACLE_SID sid
> source /usr/local/bin/coraenv
>
> HTH,
> Brian
>
> Mike Mountjoy wrote:
> >
> > 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)
> > )
> > )
> > STARTUP_WAIT_TIME_LISTENER = 0
> > CONNECT_TIMEOUT_LISTENER = 100
> > TRACE_LEVEL_LISTENER = ON
> > SID_LIST_LISTENER =
> > (SID_LIST =
> > (SID_DESC =
> > (SID_NAME =instanceA)
> > (GLOBAL_NAME = instanceA)
> > (ORACLE_HOME = /external/oracle/app/oracle/product/8i)
> > (PRESPAWN_MAX = 10)
> > )
> > (SID_DESC =
> > (SID_NAME = instanceB)
> > (GLOBAL_NAME = instanceB)
> > (ORACLE_HOME = /external/oracle/app/oracle/product/7.3.3)
> > (PRESPAWN_MAX = 10)
> > )
> > )
> >
> > 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 Fri Oct 29 1999 - 10:00:41 CDT