RE: TNS Resolution

  • From: "Dulay, Kristin" <Kristin_Dulay@xxxxxxxxx>
  • To: "'Thomas Day'" <tomday2@xxxxxxxxx>
  • Date: Tue, 24 Jan 2006 13:13:47 -0500

Thank you as well! 

I was configuring client tnsnames at the moment and we are changing domain
names - your suggestion came just in time!
It works well so the users/clients can connect with either the old domain,
new domain, or no domain in the connect string.

Kristin

 -----Original Message-----
From:   Thomas Day [mailto:tomday2@xxxxxxxxx] 
Sent:   Tuesday, January 24, 2006 10:28 AM
To:     Dulay, Kristin
Cc:     oracle-l@xxxxxxxxxxxxx
Subject:        Re: TNS Resolution

Yup.  I needed one more test.  With names.default_domain not set in
sqlnet.ora, as Kristin points out, the TNSNAMES entry with
<name1>,<name2.world> works just fine.

connect user/pwd@name1 - works
connect user/pwd@xxxxxxxxxxx - works

and in fact, if the TNSNAMES entry is <name1>,<name1.world>

then connect user/pwd@name1 works regardless of whether the
names.default_domain is present in sqlnet.ora (however, if it is
present it should be set to 'world').

Also, I have used two entries in my tnsnames to point to the same
database so that users could have their preferred alias.  That's not
necessary.

<name1>,<name1.world>,<name2>,<name2.world> in TNSNAMES allows you to
connect using

@name1
@name2
@name1.world
@name2.world

Is there no end to this maddness?

But thanks, Kristin, for testing further.  It's something that I'll
use in the future.

On 1/24/06, Dulay, Kristin <Kristin_Dulay@xxxxxxxxx> wrote:
> This works too, logging in with @db1 or @db2.world...
> db1,db2.world =
>
> am I not getting it?
>
>  -----Original Message-----
> From:   Thomas Day [mailto:tomday2@xxxxxxxxx]
> Sent:   Tuesday, January 24, 2006 9:18 AM
> To:     Dulay, Kristin
> Subject:        Re: TNS Resolution
>
> I tested it that way too and it appeared to work which is why my
> initial post was as it is.  However, if the name before the comma is
> different than the name behind the comma you will see that everything
> up to the comma is ignored.
>
> On 1/24/06, Dulay, Kristin <Kristin_Dulay@xxxxxxxxx> wrote:
> > Actually, I tested that, and it does work.  With names.default_domain
not
> > set in sqlnet.ora.
> >
> > In tnsnames:
> >
> > db1, db1.world =
> >  ......
> >
> >
> >  -----Original Message-----
> > From:   oracle-l-bounce@xxxxxxxxxxxxx
> [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
> > On Behalf Of Thomas Day
> > Sent:   Monday, January 23, 2006 9:08 AM
> > To:     Oracle Mailing List
> > Subject:        Re: TNS Resolution
> >
> > Nope.  I take it all back.
> >
> > Everything up to and including the comma is treated as a comment.
> >
> > Test twice, open mouth once.
> > --
> > //www.freelists.org/webpage/oracle-l
> >
> >
>
--
//www.freelists.org/webpage/oracle-l


Other related posts: