Re: novice Oracle 9i tnslsnr problem

"Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote in message news:D2ZV9.26656$jM5.69480_at_newsfeeds.bigpond.com...
>
> "Paul Brewer" <paul_at_paul.brewers.org.uk> wrote in message
> news:3e285cb5$1_1_at_mk-nntp-1.news.uk.worldonline.com...
> > "Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote in message
> > news:ppnV9.25058$jM5.66252_at_newsfeeds.bigpond.com...
> > >
> > >
> > > This won't work, because it's all over the place as a continuous line
of
> > > text. Lay it out properly: and I see that Karsten has already posted
> > > explaining precisely how to do that.
> > >
> > Howard,
> >
> > I don't want to pick a fight or anything,
>
> Oh, go on...
>
> >but just in the spirit of
> > experimentation, (using 816 client IIRC), I once tried putting all the
> > details for each alias on one line in the tnsnames.ora file.
>
> I may have got my wires crossed, I dunno. And I can't see the original
post
> now to check. Single lines in the tnsnames.ora, though, is perfectly
sound.
> Done that myself, not an issue. But stripping out all indentation when its
> on separate lines is a no-no, at least on Windows and Solaris.
>
> But what I thought he (the original poster) had as a single line was the
> LISTENER.ora, and although in theory that should work too, it tends not
to.
>
> >
> > It seemed to work fine. My conclusion *then* was that while I have no
> > problem with Oracle's formatting, it isn't actually necessary, since
> > carriage returns, spaces and tabs are ignored when parsing tnsnames.ora
> >
> > Was that conclusion wrong?
> >
>
> Ah, that conclusion is definitely wrong in the specific regard to the
> original post, where all lines of the tnsnames.ora were written flush
left.
> Page 13 of my paper 'creating a tnsnames.ora file' (which can be obtained
> from places that only Norman Dunbar can tell you about!!) has a specific
> worked example where I stripped out all preceding spaces, and got an
> immediate 12154 (can't resolve name).
>
> I wouldn't make any hard and fast rules about formatting (the need for it
> etc) above and beyond that. But clearly "innocent" format tweaks *can*
break
> the ability to parse tnsnames.
>
> In any case, the damn things are hard enough to read *with* the
indentation.
> Without it, I'd be thinking of having a whiskey instead.
>
> Regards
> HJR
>
>
> > By the way, I subsequently fed that 'compact' tnsnames.ora back into
9201
> > OEM and it cheerfully put all the formatting back...
> >
> > Both still work.
> >
> > Regards,
> > Paul
> >
> >
> >
>
>

Howard,

You said (in an earlier posting in this thread):

> If this is really how your tnsnames is formatted, then I'm not surprised
it
> fails to resolve the name!

My question followed this, relating to formatting of tnsnames.ora, in which I posted that as far as my (admittedly limited) experiment was concerned, carriage returns, whitespace and tabs didn't seem to make much difference (this was client-side only, using NT4 816/817).

Not trying to prove a point here, just asking, in an amicable way...

Regards,
Paul Received on Sat Jan 18 2003 - 13:22:00 CST