Re: SQL*Net from one server to another

That was *exactly* what I was suspecting. A sqlnet trace on level usually shows this immediately, as there will be an error message immediately after reading the tnsnames.ora in memory.

Regards,

Sybrand Bakker, Oracle DBA

"Harry Boswell" <staryeti_at_bellsouth.net> wrote in message news:9h84eh$bad$1_at_nntp.msstate.edu...
> Never mind and sorry to have bothered you guys - problem was a
> non-existent right paren - it only took re-reading the tnsnames.ora
> 10 or so times before I realized what I was seeing.
>
> Thanks for all the help, though...
> Harry
>
> "Harry Boswell" <staryeti_at_bellsouth.net> wrote in message
> news:9h7vf0$65b$1_at_nntp.msstate.edu...
> >
> > "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message
> > news:tjerf7rci5n675_at_beta-news.demon.nl...
> > >
> > > "Harry Boswell" <staryeti_at_bellsouth.net> wrote in message
> > > news:97275eac.0106250857.38b9419_at_posting.google.com...
> > > > I've got two Solaris servers running Oracle8 dbs; WinNT and
> > > > Win98 clients using Net80 to access the servers. All are working
> > > > fine going from Win clients to either server. But if I try to
> > > > connect from one server to another, using a database link
> > > > or just sqlplus llll/pppp_at_other_server, I get "cannot resolve
> > > > service name" errors. Do I need to do something more to get
> > > > outgoing SQL*net running on the servers?
> > > >
> > > > Thanks,
> > > > Harry Boswell
> > >
> > >
> > > The other_server service definition needs to be in the tnsnames.ora of
 the
> > > server hosting the database. Database links are server to server
 comms.
> > >
> >
> > It's there. And I can connect using that definition from the Win
 clients,
> > just not
> > from the other server. That's why I wondered if there was any further
> > Net80 definition that had to occur on a server to allow it to also be a
> > client.
> >
> > Thanks,
> > Harry
> >
> >
>
>
Received on Mon Jun 25 2001 - 17:15:01 CDT